Also note that for me personally, I don't see any value in using scripting languages for anything other than system administration instead of the more cryptic shell variants.
I have long wondered why (Common) Lisp didn't take over the world at the end of the 90s to the beginning of the millennium. :-( They have a GC, but so do Java. There were good compilers since at least the 80s.
But the lisp variants aren't really a system programming language that will replace C. (You can do bit fiddling, but... here the GC comes in, especially for embedded applications with KB of RAM. And so on.)
>> I don't see any value in using scripting languages for anything other than system administration
The point with scripting languages is that you can develop quickly. For applications where most time is in the DB anyway, they make a good solution. (I.e. for the last 20 years, system administration and web development.)
Huh? There were early Lisps with free source, too.
Also, 1, I am not a GC basher. 2. I was wondering why Lisp didn't take over most of the world 15+ years ago. Overhead was more expensive then. (And small embedded systems will always have too little RAM.)
Scripting via the UNIX shell is a poor man's REPL.
Personally I don't remember the last time I used it for anything other than setting environment variables, for anything else there are better actual programming languages.
Uhm, I still don't get why the development (/execution) environment would have been different for Lisp?
I am aware of that Unix/Linux is/was quite a simple solution. It is designed to be. It was still (more or less) the basis for Next and the present MacOS. Quite nice.
(Disclaimer: Today I really only use Linux computers, for apt and compatibility with servers. No MacOS flames, please. :-) )
> Uhm, I still don't get why the development (/execution) environment would have been different for Lisp?
I still don't get why you keep focusing this discussion on Lisp alone, I explicitly referred to several OSes.
All of them more expensive to buy than UNIX, which was available for peanuts.
As for OS X.
UNIX was the base for NeXTSTEP, because NeXT was after the workstation market owned by Sun and SGI workstations.
But anyone that has bothered to learn the NeXTSTEP stack and respective APIs, knows how little UNIX culture it had, beyond "bring your stuff to our platform".
The hybrid Mach/BSD kernel, device drivers written in Objective-C and the whole user space frameworks and GUI workflows.
Mac OS X follows that tradition as any developer committed to OS X technology stack knows.
Drivers are written in a C++ subset, we have the frameworks, automation via Apple Script, Objective-C and now Swift for GUI applications.
"This led to requests for the system, but under a 1956 consent decree in settlement of an antitrust case, the Bell System (the parent organization of Bell Labs) was forbidden from entering any business other than "common carrier communications services", and was required to license any patents it had upon request.[6] Unix could not, therefore, be turned into a product. Bell Labs instead shipped the system for the cost of media and shipping."
Also note that for me personally, I don't see any value in using scripting languages for anything other than system administration instead of the more cryptic shell variants.