I wrote this for a blog post, but I think it is relevant here. After a long comparison of a bit of code, first in Javascript and then in Clojure, I wrote:
At this point, a Javascript developer might say, “You've shown that the Functional style has some advantage, but why should I care? I can write in the Functional style using Javascript. I don't need Clojure.” That is absolutely true, and we all know that developers tend to be fiercely loyal to their languages, up 'til the moment they are not. I myself was fiercely loyal to Ruby, up 'til the moment when I wasn't. True moments of conversion are rare and always depend on a person reaching some point of pain with their current path. I myself suddenly realized that I was working with languages that would not carry me into a future full of multi-CPU computers and massive concurrency ... at which point I began to explore what the future might hold ... at which point I discovered Clojure. I would, however, counter the Javascript developer with my own set of questions. If you have realized that the Functional style is best, do you want to work in a language that undercuts that style, or supports it? Do you want to burden yourself with the extra discipline needed to pull off the Functional style in a highly mutable language, or do you want to work with a language that was designed from conception to make your life easier ? Do you want to “navigate disappointment” or travel directly in the direction of success? In his talk, “Why Clojure is my favorite Ruby,” Steven Deobald refers to dealing with pain points in a language as “Navigating disappointment.” On Thursday, July 23, 2015 at 9:04:42 AM UTC-4, Paul deGrandis wrote: > > I have had success here with a few approaches. > > For every company I work with that is new to Clojure, I provide them with > a "Quick Learn" document. The document is split into 5-7 days, and every > day they skim/read an article, poke around a resource (like ClojureDocs), > and watch a talk. Sometimes that "resource" item is an exercise or > something interactive. > > Your goal should never be to convince someone of Clojure - Clojure itself > is convincing enough. Instead motivate someone to want to learn more - get > them curious and self-driven to dive in wherever their interests lay. Get > them well adapted to the Clojure culture and the radical approach to > simplicity. Get them questioning their own practices and technologies. > Entice them with the functional approach to system creation. > > Leon mentioned my talk, which claims, "Clojure manages risk better than > any other technology" - > http://www.infoq.com/presentations/Clojure-powered-Startups > For well-established enterprise shops, I think my most recent Conj talk is > more convincing - https://www.youtube.com/watch?v=BNkYYYyfF48 > > Consider the following talks by Rich: > * Clojure, Made Simple - https://www.youtube.com/watch?v=VSdnJDO-xdg > * Are we there yet? - > http://www.infoq.com/presentations/Are-We-There-Yet-Rich-Hickey > * Simple Made Easy - http://www.infoq.com/presentations/Simple-Made-Easy > > Nothing is more convincing than a working system. If it's possible, > illustrate the virtues of Clojure and its approach to problem solving by > "walking the walk" on a small scale, where the stakes and risks are low. > Build a tool, prototype an idea in half the time it would normally take, > show the power of Protocols within your own existing system, etc. > > Regards, > Paul > > -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
