Name: Anonymous 2016-04-12 5:12
- Single threaded "cuz the 80s yo"; parallelism requires god awful, non-standard hacks
- Reliant on a proprietary product (e.g., LispWorks) to do any real project
- No libraries
- Community jerks off over "clever little hacks" instead of interesting programs
- Emacs cancer
- No libraries
Yes, macros and true metaprogramming is beautiful. But then you realize macros are only there to patch the faults of Lisp (i.e., not having a syntax) which has already been solved by other languages for several decades. The only problem that macros (weakly) solve is the fact that you're using Lisp.
Lisp's homoiconicity is actually a drawback in practice. Lisp programs are quadratically less readable and maintainable as the program grows. Every Lisper writes spaghetti code on par with PHP. That shit stopped being acceptable around 2005.
All the smart people have moved on to Haskell and FIOC.
- Reliant on a proprietary product (e.g., LispWorks) to do any real project
- No libraries
- Community jerks off over "clever little hacks" instead of interesting programs
- Emacs cancer
- No libraries
Yes, macros and true metaprogramming is beautiful. But then you realize macros are only there to patch the faults of Lisp (i.e., not having a syntax) which has already been solved by other languages for several decades. The only problem that macros (weakly) solve is the fact that you're using Lisp.
Lisp's homoiconicity is actually a drawback in practice. Lisp programs are quadratically less readable and maintainable as the program grows. Every Lisper writes spaghetti code on par with PHP. That shit stopped being acceptable around 2005.
All the smart people have moved on to Haskell and FIOC.