Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman
by lispm on Sunday November 13, 2022 @04:31AM
(#33581483)
Again the same: now there are good free Smalltalk implementations, and their adoption is not great. There are also other factors than price.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman
by dleslie on Sunday November 13, 2022 @11:17AM
(#33584413)
Scratch 1.x and 2.x were written in Smalltalk, FWIW.
But IMHO the "your whole dev environment is your shipped application" is too unappealing to catch on.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman
by lispm on Sunday November 13, 2022 @01:35PM
(#33585922)
On the Lisp side this is an extra step and a source of problems. Traditionally the commercial Lisps REQUIRE one to ship an application without the full dev environment. So there is always a delivery step which generates an application or a shared library. Some other Lisp applications require a delivery Lisp compiler, usually to C because of some other limitations: space, memory management or the platform does not allow a full dev Lisp. Example: there is a process control engine written in Lisp, which is used in industrial control applications. This Lisp application is largish and gets compiled to C and runs without garbage collection.
Re:A Brief Interview with Common Lisp Creator Dr. Scott Fahlman
by pjmlp on Sunday November 13, 2022 @12:17PM
(#33585049)
As I wrote in another thread, IBM abandoning Smalltalk for Java was the biggest blow, in a way Smalltalk was IBM's .NET to put in more modern terms, used for their IDEs (Visual Age), OS/2 RAD development and 4GL like language across all their enterprise offerings.
Until the day Java came, and they pivoted everything into Java.
0. https://gbracha.blogspot.com/2020/05/bits-of-history-words-o...