4 ms·
I 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 an
by arethuza 15y ago
I 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.
- ohyes 15y ago> C is something that works better for the average user. difficulty of using vs. difficulty of using correctly. (And I'm not even sure worse is better makes sense in a modern context). Difficulty of using a programming language (regardless of results) is inversely proportional to the amount of time spent writing code in that language. If the majority of users writes C or C++ code all day, C and C++ become 'better for the average user.' If the majority of your users write Common Lisp or Scheme all day, CL and Scheme become 'better for the average user'. C and C++ are much more difficult to actually use correctly (without regard for who the average user is), mainly because there are many more ways to screw up when you are working at such a low level. The myth of Lisp being difficult makes me boggle. There isn't even a syntax to memorize! Speed, safety, flexibility, dynamic debugging and compilation, optional static typing... You don't even need the higher level aspects of the language to reap benefits from these features. With Quick-lisp if I need a library I just load it and use it (plug and play). Why not replace my C++ and scripting languages with Common Lisp if I can get the best of both worlds? The economics of this is that if I already know Common Lisp, and am willing to teach those around me, I am a fool to use anything else.
- 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.