the Java.next project quickly turned into a deep dive into #Clojure leading to the first Clojure book, now in its third edition pragprog.com/book/shcloj3/p…
https://twitter.com/stuarthalloway/status/1025408942170693633
All the examples I wrote for the first #Clojure book still work ten years later, thanks to careful stewardship. This is stability that you can take to the bank.
People are so used to broken software that they value code churn as an indicator of health. Meanwhile #Clojure projects just work and have to add "liveness advisories" like github.com/candera/causat…
the robustness of #Clojure comes from careful, patient consideration. This consideration is mostly invisible in patches, which are a crappy medium for design collboration, but it is safe to assume that ...
... for every one hour a person spends working on a #Clojure patch, other people will have to spend an additional ten hours before any code gets merged.
Happily, #Clojure doesn't need to change. Most innovation can and should happen in libraries like spec clojure.org/guides/spec, which are composable enough that ...
... contributions to #Clojure require no centralized coordination at all. Just start a repo like github.com/bhb/expound and get cracking.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
