3 ms·
A lot have already been said about it: +Lisp Lost the train of microcomputers. They were "toy machines" that needed low level programming like assembly or fort
by cladopa 3y ago
A lot have already been said about it:
+Lisp Lost the train of microcomputers. They were "toy machines" that needed low level programming like assembly or forth or later C to do anything remotely similar to what Mainframes could do.
+Common Lisp is a mess, a compromise, like Deutsch (a language created to take something out of every variant dialect), designed by committee language. Better (opinionated, created by a person) alternative Lisps exist, like Clojure.
+Lack of (affordable, easy to use) Visual tools to develop, like Visual Studio. No. Emacs is not easy to use for newbies. Visual structured editing for parenthesis have existed for decades now but those tools were not available for normal PC and even today are very expensive, as the market for them are the companies that bought the expensive Lisp machines in low volume.
+Lack of access to the C libraries. Do you want to use anything modern like "dear imgui", iOS libraries or whatever? Bad luck.
+Competition catch up. Other languages copied(badly) the Lisp ideas, lambdas and real macros, functional programming. IMHO they did it wrong, but they are good enough for most people, while not having the problems of CL, like being able to use the C libraries as python and Lua can.
+Other Lisp are working fine. Clojure for example can use the java libraries or even some versions the C Libraries.
- siknad 3y ago> Lack of access to the C libraries. Isn't CFFI enough for that?
- Lapel2742 3y ago> Lack of access to the C libraries. ??? I recently started learning Common Lisp for fun (and fun it is!) and the ease of accessing C libraries was one of the things that surprised me in a positive way. Using https://github.com/rpav/cl-autowrap https://github.com/rpav/cl-autowrap one can simply write (c-include "file.h") and the API defined in "file.h" is accessible from Lisp. I can't think of a simpler way. Even without cl-autowrap, FFI using https://cffi.common-lisp.dev/ https://cffi.common-lisp.dev/ seems simple enough.
- panick21_ 3y agoI think he was talking about the late 80s and the 90s.