3 ms·

In a market share sense, Linux doesn't and never existed in the desktop in first place. However it's ubiquitous in servers and that success has nothing to do wi

by natrys 4y ago

In a market share sense, Linux doesn't and never existed in the desktop in first place. However it's ubiquitous in servers and that success has nothing to do with a DE. Its universal success in server space also means many more people are acquainted with Linux today than Lisp in its heyday. If you consider the current 2% market share in desktop to be "existing", I will posit that these people aren't going away just because of fragmented UI, because I believe bulk majority of them are spill over technical users who use Linux despite the state of DE.

Ygg2 4y ago
I'm not referencing the market share. I'm referring to Lisp Curse. http://www.winestockwebdesign.com/Essays/Lisp_Curse.html http://www.winestockwebdesign.com/Essays/Lisp_Curse.html In summary: Because Lisp was easy to fork, any time two nerds disagreed it was forked. And because they weren't working on same database you got Lisps with patchworks of functionality/bugs that each on their own couldn't compare to more or less monolith language like C/C++ or Java. Same dynamic in Linux land. So instead of having 1000 developers on one codebase we have 100 on ten different DE, windowing system, etc. Rather than having one sound system we have a dozen... It doesn't work on PulseAudio, try OpenSound, no wait OSSBlasterMaster...
- anthk 4y ago
  Scheme and Common Lisp are different environments altogether, Also, Emacs Lisp has a good chunk on fuctions backed it. >s that each on their own couldn't compare to more or less monolith language like C/C++ or Java. Good joke. On C++, Boost. Try to compile older C++ code from 2006 today, it may fail spectacularly. A lot of older C++ games from 2006 will be damn difficult to compile today. On Java, heh. Different and incompatible JRE's. Software tied to a single JRE where it crashes on the newer ones. Should I go on? Meanwhile, 20 yo Elisp code still runs today as-is.

by natrys 4y ago

Ygg2 4y ago

I'm not referencing the market share. I'm referring to Lisp Curse. http://www.winestockwebdesign.com/Essays/Lisp_Curse.html http://www.winestockwebdesign.com/Essays/Lisp_Curse.html In summary: Because Lisp was easy to fork, any time two nerds disagreed it was forked. And because they weren't working on same database you got Lisps with patchworks of functionality/bugs that each on their own couldn't compare to more or less monolith language like C/C++ or Java. Same dynamic in Linux land. So instead of having 1000 developers on one codebase we have 100 on ten different DE, windowing system, etc. Rather than having one sound system we have a dozen... It doesn't work on PulseAudio, try OpenSound, no wait OSSBlasterMaster...

anthk 4y ago
Scheme and Common Lisp are different environments altogether, Also, Emacs Lisp has a good chunk on fuctions backed it. >s that each on their own couldn't compare to more or less monolith language like C/C++ or Java. Good joke. On C++, Boost. Try to compile older C++ code from 2006 today, it may fail spectacularly. A lot of older C++ games from 2006 will be damn difficult to compile today. On Java, heh. Different and incompatible JRE's. Software tied to a single JRE where it crashes on the newer ones. Should I go on? Meanwhile, 20 yo Elisp code still runs today as-is.