4 ms·
it is still Yegge: shallow and mostly wrong. People who actually use Lisp (opposed to people who only write about it) have no problem that there are extensions
by lispm 17y ago
it is still Yegge: shallow and mostly wrong.
People who actually use Lisp (opposed to people who only write about it) have no problem that there are extensions to the standard. The whole point of Lisp is that it is easily extended in many ways: the programmable programming language. Sure it brings a bunch of problems, but that's what it is and why people use it.
The stuff he writes about CLOS is mostly wrong. CLOS is not implemented as a bunch of macros. CLOS is actually a three level architecture: the core is written object-oriented in CLOS itself, on top is a functional interface and for user convenience there is a bunch of macros for easy definition of classes, generic functions, methods and some other language objects.
Then, macros are no problem. They are a feature. No, 'hygienic' is fine, but not needed. No they don't need to be rethought. They do a useful job like they are.
No, Lisp will never be massively successful (because it is a bit too complicated, too dynamic, too powerful for many users) and bending the language trying to make it 'massively successful' won't improve anything. No, I don't want a dictator. Lisp has choice, various alternatives and a more democratic approach.
Lisp is still a good choice for computing with symbols. If you don't need that, then you might not need Lisp. But that's not a reason that Lisp should change. Should a helicopter be changed in design because someone does not use it, but drives a car? Should the helicopter be changed, because more people drive cars, getting a drivers license for cars is easier than getting a pilot's license for helicopters? Lisp is different, for a reason and this difference will ensure its survival for many years. We have now fifty years that the basic ideas have proven to be useful and I don't see that this will change in the coming years.
- andreyf 17y agobending the language trying to make it 'massively successful' won't improve anything This needs to be repeated more often - quality isn't measured by popularity. It's obvious when we talk about food establishments (McDonald's being the equivalent of Java), but for some reason, the logic is completely lost on people when we start talking about programming languages.
- lispm 17y agoif you are a good cook, a sharp knife will be very useful. Others might only hurt themselves with it. No, the quality of things is not measured necessarily by the amount of uneducated users.
- anonjon 17y agoBad analogy. Even if you are a mediocre cook, you are more likely to cut yourself with a dull knife than a sharp one, because it won't cut as well (and will slip, maiming your fingers). Also you'll improve faster, as the easy/boring jobs like chopping onions will go by faster. Seriously, spend the money on a good knife.
- arohner 17y ago> if you are a good cook, a sharp knife will be very useful. Others might only hurt themselves with it. Therefore inexperienced cooks should prepare food with butter knives?
- lispm 17y agojust avoid sushi where you need real sharp knifes
- zaphar 17y agoA better way to state this is that if you are a good cook you are willing to spend more on a quality sharp knife. If you aren't a good cook you'll probably buy the serrated surgical steel knife from the guy in the mall because it's only 19.95 and will "stay sharp for life". Lisp has a cost for useage. Higher learning curve, Different way of thinking about patterns. Harder to use correctly at first. It's worth it for the "good cook" to pay the cost. Maybe not for the everyone else. (as an aside I love my expensive set of high quality knives. and always feel handicapped when I have to cook without them. But they did cost a small fortune)
- brlewis 17y agoI really think if you plan on programming for more than a year, the learning curve for Scheme or CL is worth it. I was at the jQuery conference this past weekend, and a lot of the functional programming concepts would be way easier for people to understand if people saw them in Scheme first.
- lsd5you 17y ago<i>(McDonald's being the equivalent of Java)</i> Is this true, or is it something you want to be true. I would say its a disservice to the language which in many ways was better than its peers and has since been imitated a lot (VMs, Javadoc, Parts of the platform library). The tools in terms of breadth and quality available for java (IDEs, testing, decompiling, AOP ... etc.) are years ahead of most other platforms. (Excluding C#, what else...?). A large part of this is due to the simplicity of the language (and the stability). Is java worse if you are developping in Vim, no doubt, but this is a strawman. With the tools vs. python|ruby|lisp is a different proposition entirely.
- lispm 17y agoJava appealed to the industrial users: a controlled language specified down to the instruction level, no complicated features, absolute stability on all levels. The SUN Java courses were just that: the programmer has to learn the language constructs and the library. Then the programmer learns some patterns to use the language effectively Lisp is the antithesis to this: it is a language laboratory - the programmable programming language. The programmer needs to develop skills to understand when and how to change the language. Changing and extending the language is a core mechanism. This makes the language unstable and puts a lot of linguistic power into the programmer. With Lisp you need to trust the programmer and the programmer has to learn how to justify the trust (by learning to effectively use macros, by learning when and when not to use EVAL, ...). The Lisp programmer has to learn how to program languages and the concepts he may want to use for that.
- lsd5you 17y agoI don't really disagree, though it is a bit of a simplification. There is a lot to this argument, but without going into details (another time maybe) is it not a testament to the base of the language that they've managed to build so much crap on top of it??.
- andreyf 17y agois it not a testament to the base of the language that they've managed to build so much crap on top of it? No, that's just a question of marketing and man power.
- kevbin 17y agoI think Java™ is more like Starbucks® Java:Starbucks::C#:Coffee Bean & Tea Leaf Java:Starbucks::Scala:Peets Java:Starbucks::Groovy:Mystic Mocha Java:Starbucks::Algol60:Vesuvio Café
- berntb 17y ago>>Lisp will never be massively successful (because it is a bit too complicated, too dynamic, too powerful for many users) I have a hard time buying your explanation, since the scripting languages of today can be described as lisp subsets. I am a fan of Perl and enjoy my life. The other usual scripting languages are quite similar, in most ways. Still, I'd love to get a job using Common Lisp, which I haven't really touched since I studied. Why can't I do that? Edit: I don't mean to whine, it is just that there is something wrong here. Lisp should be a, well, "contender".
- felideon 17y agoStill, I'd love to get a job using Common Lisp, which I haven't really touched since I studied. Why can't I do that? Because, in the words of Drew Crampsie (paraphrased): Lispers do not look for Lisp jobs. They look for work to do and do it in Lisp. Edit: Also, I believe well-established Lisp companies (such as ITA or Clozure) usually look for experienced Lispers. If you studied it in school, what makes you a good candidate for these companies?
- berntb 17y agoThanks for good information, but it wasn't what I asked about. :-) Lots of the standard scripting jobs out there could be done at least as well with lisp, so why aren't many of them? (For instance, there has been good interpreting and compiling environments for Lisp since the 1980s? 1970s?) (I didn't have any Common Lisp courses, I studied another lisp. I learned CL by myself.) Edit: A bit of syntax.
- revorad 17y agohttp://www.paulgraham.com/iflisp.html http://www.paulgraham.com/iflisp.html
- gaius 17y agoThe argument that Lisp is too complicated for the average programmer is clearly nonsense: Anyone smart enough to use C++ to a professional standard is certainly smart enough to use Lisp. It's just sour grapes.
- jaytee_clone 17y agoWhile I agree with your sentiment mostly, I feel Lisp's un-popularity probably has nothing to do with Lisp itself. For that matter, mainstream popularity of anything has always had a good dose of randomness in it (I bet you can model it with some sort of free energy / entropy equation). For example, it's hard to break down exactly why the No.1 hit song is No.1, or that No.7 song is permanently No.7. Usually it has more to do with the politics of the record company than the quality of the song itself. We are also being a bit pessimistic here. Lisp is not un-popular. It just hasn't reach the critical mass yet. And it seems to be going to that direction with unraveling of Clojure.
- jimbokun 17y agoI agree with him about "which implementation?" and "worthless spec." I have yet to hear a valid reason for why a modern standard library for Common Lisp is a bad thing. There are lots of reasons for not doing this, but they are all political in one way or another, not technical. I agree with you that CLOS and macros are not problems. Common Lisp is not primarily an object oriented language, and that's OK. That it happens to have an extremely powerful object system is a nice bonus. If you want a ground up object system, use Smalltalk or Ruby and have fun. The rant against macros was incoherent to me. Editor support for macros is imperfect so...macros suck...or something? Macros remain the distinguishing feature of Lisp, in that no other language allows you to transform your source code so seamlessly. I'm not sure there's a compelling reason to use any Lisp over other languages if macros are eliminated.