3 ms·
I 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 b
by jimbokun 17y ago
I 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.