|
|
|
|
|
|
by dustingetz
2453 days ago
|
|
|
John deGoes said "Clojure developers ... consciously stay inside the Clojure community because they love the language and ecosystem" and I think that's pretty interesting – Clojure has like this event horizon where if you cross it, you become so attached to it that you never leave. It's like a little black hole that is already self-sustaining – it can only grow, it will never die, and it can happily wait for opportunity. We think of hockey stick tech adoption curves as smooth exponentials, but that's not actually true. Hockey sticks demonstrate COMPLIMENT EFFECTS, which is where the latent potential for growth is suddenly activated by an external trigger. An example is broadband/youtube, described by VC Chris Dixon here: http://cdixon.org/2009/09/10/non-linearity-of-technology-ado... Another is smartphones and smartphone apps. Ruby/Rails. Scala/bigdata. Our goal at http://www.hyperfiddle.net is to use the low-code movement to trigger complement effects in Clojure. |
|
|
About a year later, I was doing a project where I felt a dynamic language would be useful, still wanted it to be pure-functional-ish, and tried Clojure, and this time started with the fundamentals, and once I got to macros, I was completely hooked on Lisp for forever.
I thought it was the coolest thing ever that I could add language features without having to understand compiler theory or anything like that.
=====
Nowadays, my work involves around 50% Java (yuck) and 50% Clojure, but a lot of my personal projects are done with Scheme, since I have to admit that I do kind of like the `define-syntax` macro system better than Clojure's.
I definitely see the "event horizon" analogy. Once you see just how much more productive you are with the language than most others, it's hard to leave.