I've reposted your message on Russian <a href="http://gzip.rsdn.ru/Forum/Message.aspx?mid=2074189&only=1">rsdn.ru</a>.<br><br>One of the <a href="http://gzip.rsdn.ru/Forum/Message.aspx?mid=2075163&only=1">questions to this post is
</a>: which problems, exactly, are unsolvable, or hard to solve with modern languages? Not specific Lisp hacks, but a list of real-life problems would be nice.<br><br>:)<br><br>On 8/24/06, Rudolph van Graan <<a href="mailto:email@example.com">
firstname.lastname@example.org</a>> wrote:<br>> Hi Guys,<br>> <br>> This whole topic interest me greatly. Unfortunately I've not been<br>> part of the Lisp generation ;) - my only experience in Lisp stems<br>> from the fact that I had to make emacs work for me. To date Lisp is
<br>> the greatest mystery ever. I've managed to salvage one good book<br>> which someone else threw away, written in 1982 "Lisp" by Winston and<br>> Horn. What amazes me is the type of problems solved in the late
<br>> seventies. From the TOC:<br>> <br>> Chapter 18: Lisp in Lisp (Building an interpreter)<br>> 24: Symbolic pattern matching<br>> 26: Rule based expert systems and forward chaining<br>> 30: Procedure writing programs
<br>> <br>> etc<br>> <br>> What worries me is that the "old" languages managed to do things that<br>> are nearly impossible or very difficult (in my opinion) to do in<br>> modern languages. How come the Javas and C#'s etc lost these
<br>> abilities and be called modern?<br><br>...<br><br>> Back to my original point - what kind of abilities did we lose going<br>> from Lisp/Smalltalk into the VB's/Delphi's/C++ into Java/C# etc that<br>> are now being reinvented in a bad way in the new "languages"?
<br>> <br>> <br>> Rudolph<br>> <br>> <br>> <br>