3 ms·
Maybe somebody does it like Rich Hickey, coming from C++, checking out CL for some time and then moving on. But it transformed him. The next generation may look
by lispm 7y ago
Maybe somebody does it like Rich Hickey, coming from C++, checking out CL for some time and then moving on. But it transformed him. The next generation may look at Clojure, check it out some time and then move on to design the next thing... it might then be helpful to understand where SOME (by far not all) of the ideas originally were coming from...
- iLemming 7y agoAs I said: "CL is Latin of Lisps". If you're a language designer you definitely should know it. But using a very dense language with too many features for app development, in practice, often causes more issues rather than solving problems. Clojure is opinionated and that's a good thing.
- lispm 7y agoClojure has the 'half' of its features on the Java side. The whole package is a huge Java infrastructure with zillions of features + Clojure. Common Lisp was designed to be that on its own, and its actually not that large anymore - compared to similar options. Everyone who wants to learn a Lisp which stands on its own feets - for example SBCL has only a relatively small C core and all the rest is Lisp itself - should have a look. This has deep effects generally for Lisp: better error handling, better interactivity, images, simpler debugging, less language compromises on the low-level, ... Lisp is also not opinionated. Working in a non-opinionated languages is different. In Lisp the developer may need to develop his/her own opinions. Right now you are looking at a shallow image of Lisp.