Why Ruby is an acceptable Lisp (2005)
For a 2005 article, this is totally awesome, as well as that Steve Yegge response. But in 2016, it&#x27;s hard for me not to get excited about what&#x27;s seeming like Clojure&#x27;s upward trajectory into the mainstream and want to jump on board 100%. To paraphrase Rich Hickey, Lisp and immutable functional programming totally rock, and the JVM and Javascript just reach (ClojureScript). As our systems get bigger and more quality is demanded from our software, it&#x27;d be so cool if we could get behind this as a standard, in all the growing technology fields -- web and mobile (Om.next for React and React Native), big data, AI&#x2F;machine learning, Dockerization&#x2F;containerization and even decentralized stuff (Pelle Braendgaard&#x27;s Cloth library for Ethereum is a start, and I was just talking with some awesome people in the Clojure Slack channel working on Boot tasks for IPFS, and soon the Golem Network project will be launched which will be super dope). Hell, even designers can start designing in Clojure now. It&#x27;s just Simple, and as the community grows, rallying behind it is only going to get Easier. People were raving with React Native about how JavaScript developers could now all the sudden start coding mobile apps. How cool would it be if there was just one awesome language, the one true immutable functional Lisp, where everybody in tech could understand each other and collaborate? I genuinely think this is Lisp&#x27;s revenge (shoutout David Nolen!).<p>It&#x27;s been tough for me as a new developer to learn this stuff without nearly as many resources as there are in the Python and Ruby communities for beginners, but there&#x27;s no question this is the (near-term) future. Plus, a lot of that stuff just complects everything anyways and doesn&#x27;t have to apply anymore (read: mutable state, no Value on Values).<p>Let&#x27;s keep it Lispy. ;)