Unix isn&#x27;t for end users, it&#x27;s for developers to build on top of to give things to end users. Linux on desktop already happened years and years ago if you work for a tech company, and that&#x27;s probably about as far as it needs to go.<p><a href="http:&#x2F;&#x2F;steve-yegge.blogspot.com&#x2F;2006&#x2F;04&#x2F;lisp-is-not-acceptable-lisp.html" rel="nofollow">http:&#x2F;&#x2F;steve-yegge.blogspot.com&#x2F;2006&#x2F;04&#x2F;lisp-is-not-acceptab...</a><p>This is Steve Yegge&#x27;s understanding of the Lisp community, and I should clarify that I don&#x27;t think the XML monstrosities we all work with are &quot;all their fault&quot;, but that, on the whole, the Lisp community and enterprise coders were mutually antagonistic.<p>Javascript after ES3 really wasn&#x27;t broken at all, just most people coding in it didn&#x27;t know how to take advantage of it. No language can prevent someone dedicated to bad code architecture from writing bad code. A Lisp programmer would&#x27;ve found a lot of comfortable features and powerful patterns and been able to share them, but most of their efforts were wasted denouncing everyone outside of their tiny sect. The end result was that most people learning JavaScript were taught how to code like it was broken Java because most of the resources were written by Enterprise Java devs who didn&#x27;t understand what a fundamentally impoverished language Java is.