5 ms·
This is exactly the kind of cultish triumphalism that put me off Common Lisp. The inability of many lispers to see lisp, like all languages, as a collection of
by cageface 16y ago
This is exactly the kind of cultish triumphalism that put me off Common Lisp. The inability of many lispers to see lisp, like all languages, as a collection of design tradeoffs instead of the one true way just clashed too sharply with reality for my tastes.
It's certainly true that lisp has been an important testbed for many concepts that have later made their way into the programming mainstream, but I suspect that many of the traits that make a good research language may actually be undesirable in a production language.
- neptun 16y agoCommon Lisp is not a research language. The goal of the comitee was to produce a language fit to industry needs.
- tomjen3 16y agoThen I urge you to look at it again - who cares what the users believe? What matters is what you get out of it.
- cageface 16y agoI hacked a lot of CL back in 2002-2003 and I've dabbled in Clojure lately. Clojure has a lot of promise but I'm waiting for some of the rough edges to get smoothed out (stacktraces in particular).
- gphil 16y agoI agree about Clojure's rough edges. I'm a beginner, and when something goes wrong it is very opaque to me what happened. That said, I do enjoy the language--especially the baked-in data structures.
- swannodette 16y agoIf you're adventurous enough to try out the 1.3 alphas you'll find the stack traces immensely improved.
- swannodette 16y agoAs Lisp is very good at adopting paradigms from other languages - the only design tradeoff that I've consistently heard is the syntax - and this usually from people too blind to realize their syntax is hardly better. So what do you see as a fundamental design tradeoff for Lisps?
- cageface 16y agopeople too blind to realize their syntax is hardly better That's exactly the kind of categorical statement I'm so tired of hearing from lispers. Other syntaxes score better on every metric (terseness, readability, expressiveness) except flexibility. Lisp makes the same design tradeoffs the other dynamic languages do but bets the farm on macros. Over 40 years of historical evidence suggests that most programmers do not find the power of macros adequate compensation for a syntax they find highly unpalatable. It takes a special kind of arrogance to dismiss all of these people as blind.
- swannodette 16y agoExcept syntaxes die. Syntaxes tend to encode what is possible to describe in a particular language. Eventually people decide what a language expresses is not adequate, they write a new language w/ new syntax to describe a new thing. Lisp adopts the new thing with little in the way of syntactical change. How do you account for that? * Over 40 years of historical evidence suggests that most programmers do not find the power of macros adequate compensation for a syntax they find highly unpalatable. It takes a special kind of arrogance to dismiss all of these people as blind. No 40 years of historical evidence suggest that your syntax will die. C and C++ have survived because of their intimate nature w/ popular operating systems. Lisp has survived because it can evolve. How can you not chuckle that C and C++ are just now getting lambdas and closures? In anycase Alan Kay says it better than I, http://queue.acm.org/detail.cfm?id=1039523 http://queue.acm.org/detail.cfm?id=1039523.