4 ms·
A good read, but it is opinionated in an opposite direction to my own experience. Almost half of my consulting work in the last 18 months has used Clojure. Base
by mark_l_watson 15y ago
A good read, but it is opinionated in an opposite direction to my own experience. Almost half of my consulting work in the last 18 months has used Clojure. Based on the quality of projects written in Clojure and some very good decisions that Rich made, Clojure's developers' market share will continue to grow.
That said, Common Lisp is a great platform and for some applications, Scheme is a fine language choice. Common Lisp has a high learning curve and many developers will not want to invest the resources to master it. About 10% of my consulting work in the last 10 years or so has used Common Lisp and before that I used some form of Lisp for many projects at SAIC starting in the early 1980s. Although the Scheme library situation is getting better, I personally use Scheme for my own small projects that tend to be all new code, often just to think about a problem. Gambit-C with its custom Emacs interface is probably my favorite coding/experimenting environment.
I would say that the future of Lisp is looking good.
- arethuza 15y agoI did think he was a bit harsh on CL - it may be the ultimate "big ball of mud" programming environment but there are some truly lovely parts to it (CLOS/MOP and the loop macro being my favourites). "APL is like a beautiful diamond - flawless, beautifully symmetrical. But you can't add anything to it. If you try to glue on another diamond, you don't get a bigger diamond. Lisp is like a ball of mud. Add more and it's still a ball of mud - it still looks like Lisp." http://en.wikipedia.org/wiki/Big_ball_of_mud http://en.wikipedia.org/wiki/Big_ball_of_mud
- numeromancer 15y agoCLOS/MOP and the loop macro being my favourites I agree with CLOS & MOP, but the loop macro is more like a pair of scissors that has been stuck into the Big Ball of Mud; it doesn't fit in with anything else, and makes it harder to use it for what it is really good for.
- arethuza 15y agoYeah - I appreciate that the loop macro is a bit like a wee looping DSL that has been bolted onto Lisp!
- ohyes 15y agos/ CLOS and MOP seem like they are welded on to an otherwise good language, whereas loop is beautiful in all its loop DSL glory. /s (In truth, I find that both have their uses). Basically, different people disagree about which part of Common Lisp it is that they dislike. Unfortunately, this leads many people to believe that Common Lisp is not a very good language for programming in. To the contrary, people simply end up with very strong opinions about the different parts of Common Lisp that they _do not yet_ understand. This is largely because it is trivial to implement your own object system or loop construct, so people think about the language in a completely different way. There is a mentality of 'Hey, I could do this better than what the standard does.' You think about the way languages work differently. My evidence for this is that I have never seen a C++ programmer complain about the for loop and describe a better for loop, you rarely see java programmers talking about how much better a different object system would be.
- numeromancer 15y agoI have never seen a C++ programmer complain about the for loop and describe a better for loop, you rarely see java programmers talking about how much better a different object system would be. Amen to that! Except... I'm a C & C++ developer who sometimes complains about for-loops, and often pines for dynamic dispatch. And any C developer who has written or used a FOR_* macro has complained about for-loops, whether she knows it or not. In CL, I prefer iterate.
- syntaxfree 15y agoAgain, this is covered in RPG's "Good news, bad news" (I'm busy, google it) and, to a lesser extent, "The bipolar Lisp programmer". RPG's main argument is that Lisp is "MIT-style" the Right Thing, while C is "New Jersey-style" solve-the-right-problem-at-the-right-level. In other words, Lisp is like an expensive speaker system that's hard to configure correctly for ordinary sound systems, while C is something that works better for the average user. The economics upshot of this is: target Lisp at the high-level critical applications Erlang and Haskell are targeting -- big telecom routing logical problems, flexible quant finance modelling, etc. Stop trying to replace the Scripting Language du Jour. You can't compete against C++; it's everywhere from Facebook to Arduino.
- TeMPOraL 15y agoIt's important to look at the "In programming languages" section - http://en.wikipedia.org/wiki/Big_ball_of_mud#In_programming_languages http://en.wikipedia.org/wiki/Big_ball_of_mud#In_programming_... - because there, 'big ball of mud' means something else that one would think at a first glance, and the quoted statement does not use 'big ball of mud' as a negative description; it refers to its malleability.
- cageface 15y agoWhat kinds of consulting opportunities are there for Lisp people? I don't see a lot of postings for those skills but maybe it's a more specialized market?
- mark_l_watson 15y agoI get consulting offers through my web site, where I have some Lisp related materials. I guess that is how people find me.