C
ccc31807
Got 'Seven Languages in Seven Weeks' by Bruce Tate for Christmas and
have just finished my first quick read through. It's a pretty easy
read if you don't pay attention to understanding the code, and well
worth reading through.
My initial impression is that big, general languages for solving
general programs (like C++ and Java) will probably become less
important, while small, specialized languages for solving particular
problems will become more important. I can see developers knowing a
dozen languages, which they would use in their work, much as a
carpenter would use a saw, hammer, wrench, etc. In fact, we already do
(HTML, SQL, CSS, JavaScript, LaTeX, XML, etc.) The chapter on Prolog
really showed me how a hard problem is easy with the right tool.
I use Perl mostly for database stuff, munging data, producing reports,
etc. I am not a developer or programmer -- just someone who uses Perl
as a tool to accomplish everyday tasks. As I read through 'Seven
Languages' I thought about how I could use each language in my work.
Each language has its strengths, but for particular jobs, Perl can't
be beat. Obviously, each language can best solve the class of problems
it was designed for ... but this includes Perl as well.
The other thing that struck me was the problem of deploying programs
to users. If you can't compile a program to an executable (using C,
perhaps), or bytecode for the JVM or CLR, you are pretty much out of
luck. I think that languages like Scala and Clojure, which target the
JVM, will continue to attract new users. Unfortunately, you can't
write a program in Perl, have a lay user install it on the machine,
and have it run with nothing more (as you can an exe, or a program
compiled to run on the JVM or CLR.) This is a big obstacle for Perl.
Anyway, I enjoyed my first reading of 'Seven Languages.' I can't say
that I'll study all seven, but several have piqued my interest enough
to put them on my private calender for a closer look (Erlang, Clojure,
Ruby, and Prolog).
All the best for the coming New Year, CC.
have just finished my first quick read through. It's a pretty easy
read if you don't pay attention to understanding the code, and well
worth reading through.
My initial impression is that big, general languages for solving
general programs (like C++ and Java) will probably become less
important, while small, specialized languages for solving particular
problems will become more important. I can see developers knowing a
dozen languages, which they would use in their work, much as a
carpenter would use a saw, hammer, wrench, etc. In fact, we already do
(HTML, SQL, CSS, JavaScript, LaTeX, XML, etc.) The chapter on Prolog
really showed me how a hard problem is easy with the right tool.
I use Perl mostly for database stuff, munging data, producing reports,
etc. I am not a developer or programmer -- just someone who uses Perl
as a tool to accomplish everyday tasks. As I read through 'Seven
Languages' I thought about how I could use each language in my work.
Each language has its strengths, but for particular jobs, Perl can't
be beat. Obviously, each language can best solve the class of problems
it was designed for ... but this includes Perl as well.
The other thing that struck me was the problem of deploying programs
to users. If you can't compile a program to an executable (using C,
perhaps), or bytecode for the JVM or CLR, you are pretty much out of
luck. I think that languages like Scala and Clojure, which target the
JVM, will continue to attract new users. Unfortunately, you can't
write a program in Perl, have a lay user install it on the machine,
and have it run with nothing more (as you can an exe, or a program
compiled to run on the JVM or CLR.) This is a big obstacle for Perl.
Anyway, I enjoyed my first reading of 'Seven Languages.' I can't say
that I'll study all seven, but several have piqued my interest enough
to put them on my private calender for a closer look (Erlang, Clojure,
Ruby, and Prolog).
All the best for the coming New Year, CC.