Successful Lisp: How to Understand and Use Common Lisp

Re:Successful Lisp: How to Understand and Use Common Lisp by mahmud on Monday January 10, 2011 @04:57AM (#2087995)

No. I would use Scheme where I need to have absolute control over the application along with the implementation. That includes any type of hardware hacking, full-stack networked distributed apps, mobile apps, gaming platforms, experimenting on new OSes, etc.

Common Lisp is better on maturer platforms, while Scheme is like a little wedge that you can slip into cracks to open it wider, before you sneak in more and more Lisp. See how Kawa does Java applets while Common Lisp does the web server, etc.

Common Lisp is the 1-wood/driver, Scheme is the putter. To use a golf analogy. (and sadly, many of the people that advocate scheme-everything don't have messy problems; their ball is already on the green, so to speak.)

[ Parent | on HN ]

Re:Successful Lisp: How to Understand and Use Common Lisp by lanolin on Monday January 10, 2011 @08:42AM (#2088409)

This discussion seems to focus on the plain spartan Scheme standard, when -- comparing to CL -- it should focus on an implementation that contains standard-ish libraries as well.

Although CL might be the whole well-stocked golf bag (1-wood, 2-wood, irons, wedges, putters, ball-cleaner, radio...), wouldn't, say, Chicken be a smaller but still fairly well-rounded set?

[ Parent | on HN ]

Re:Successful Lisp: How to Understand and Use Common Lisp by mahmud on Monday January 10, 2011 @09:27AM (#2088527)

Chicken is the size of Common Lisp, but without the benefit of standard specification or a community.

What exactly are arguing about then?

[ Parent | on HN ]