|
Authored by: Anonymous on Monday, July 23 2012 @ 07:42 PM EDT |
I only dabble in Python; can someone explain how it is more like Lisp than
Perl?
[ Reply to This | Parent | # ]
|
|
Authored by: Anonymous on Monday, July 23 2012 @ 07:48 PM EDT |
All of these languages are designed to be interpreted first,
compiled maybe (but only partially). Like LISP before them,
they don't excel at speed and precision, but at alleged
"ease of use" (for throw away tasks and bad programmers).
Java even had a short blooming of hardware-mostly machines,
just like LISP had 15 years earlier.
And sure, some important projects came from people in love
with those platforms (GNU, Eliza, SAX, Mobile code in
browsers).
As a rule of thumb, languages with a source-code-
understanding "eval" function and/or a complete "reflection"
feature and/or typeless variables generally belong to this
category. Those 3 are the most common pieces of oversize
baggage that prevent languages from producing anything
resembling full speed efficient programs for non-crippled
hardware of its age.
[ Reply to This | Parent | # ]
|
|
|
|
|