3 ms·
Surprising that you mention this with Clojure. Do you find the churn to be from libraries or within the project code itself? The Clojure language and core libr
by wilsonthewhale 6y ago
Surprising that you mention this with Clojure. Do you find the churn to be from libraries or within the project code itself?
The Clojure language and core library is extremely stable, almost uncannily so. I can't think of any major upheavals it's had for a long time. Transducers from 1.7 maybe? But those fit in with the rest of the core library and didn't cause any issues.
- jjuliano 6y agoThe problem is not the language being stable or mature. I'm sure Ruby has been around since 1995, Lisp existed even before my parents. With Lisp, you can create a "Hello World" program in variety of multiple ways. Sure you can refactor it, starting with how to print the letter "H", throw UTF-16 support there as well. At the end of the day, you wasted precious time and resources printing "Hello World". Doing things in variety does not mean value. Doing it right the first time means value, now imagine if it's a team.
- gnufx 6y agoI don't recognise the picture of Lisp programming qua Lisp. "Refactor" probably wasn't even a word you'd hear for most of Lisp's existence. The Common Lisp standard definition is clearly not churning. I used to have a mail signature when Python was relatively new There should be only one way to do it. -- Python There's more than one way to do it. -- Perl Do the right thing. -- Lisp