5 ms·
For me Lisp was a lot of fun to learn and play with, but I dont think it had a chance to survive in modern production environment because: 1. Not typed 2. Absen
by alde 7y ago
For me Lisp was a lot of fun to learn and play with, but I dont think it had a chance to survive in modern production environment because:
1. Not typed
2. Absence of a proper package mechanism and package managers like cargo or npm
- pfdietz 7y agoI was just thinking that far from "not surviving", one of Common Lisp's great advantages is that it's difficult to see how it could die. The free implementations have achieved a remarkably level of maturity and polish, particularly SBCL. Your first point there seems weird, giving the growing market penetration of Python.
- flavio81 7y ago>because: 1. Not typed Umm... the long section on "Common Lisp: The language" describing the features of the type system disagree with you. > 2. Absence of a proper package mechanism and package managers like cargo or npm Quicklisp.
- alde 7y agoCL has some type checking features in some of its compilers, but this doesnt mean it is a typed language. Quicklisp is still in beta and is in no way even close to package managers like cargo or npm.
- flavio81 7y ago>but this doesnt mean it is a typed language Custom data types can be defined Data types can be checked, Functions can be dispatched on the data type of the input parameters (see CLOS), Variable types can be declared. ... so, Lisp isn't a "typed language"? >Quicklisp is still in beta and is in no way even close to package managers like cargo or npm. QL is already better than NPM and PIP. It says "beta" only because the author is modest; it already has years of releases and development. Maven is a better package manager, though.