News for hackers. Stuff that matters.
Re:Racket: The Lisp for the Modern Day by wildermuthn on Thursday June 29, 2023 @09:31AM (#36520105)
Unfortunately, IMHO Clojure’s maintainers hold an iron grip on the language and actively limit the growth of an ecosystem around it. See “Open Source is not about you”.

It’s too bad, because itself is really terrific.

Re:Racket: The Lisp for the Modern Day by pjmlp on Thursday June 29, 2023 @09:58AM (#36520439)
To their right, Rich Hickey almost got bankrupted while developing Clojure.

The usual "expect all for free, give nothing back" attitude.

Re:Racket: The Lisp for the Modern Day by threatofrain on Thursday June 29, 2023 @10:29AM (#36520825)
Rich Hickey basically wrote this in response to one of the notable and respected contributors of his ecosystem (Chas Emericks). If Rich wanted open source to be nothing more than a license and delivery mechanism then he shouldn’t have accepted volunteers. But a language without an ecosystem of volunteers is a dead language.
Re:Racket: The Lisp for the Modern Day by pjmlp on Thursday June 29, 2023 @11:23AM (#36521654)
Many languages do quite well as commercial products.
Re:Racket: The Lisp for the Modern Day by erichocean on Thursday June 29, 2023 @11:24AM (#36521675)
Clojure "the language" is certainly ossified, but Clojure "the ecosystem" is doing very, very well.
Re:Racket: The Lisp for the Modern Day by nocman on Thursday June 29, 2023 @01:06PM (#36523297)
I'm genuinely curious. What about the language do you feel is "ossified"? I am interpreting that as being a negative description.

Stability is extremely valuable. A lack of change to the core language over extended periods of time can be a very good thing, especially if certain changes would break existing code. Rich has made it clear that he is indeed targeting this kind of stability.

Again, I would be very interested to hear what specific changes you think need to be made to 'Clojure "the language"'.

Re:Racket: The Lisp for the Modern Day by erichocean on Thursday June 29, 2023 @03:52PM (#36525810)
No changes, I'm a happy Clojure user. Long-term stability is one of its selling points.
Re:Racket: The Lisp for the Modern Day by nocman on Tuesday July 11, 2023 @09:38AM (#36680795)
Been busy and didn't see the response...

So... you meant 'ossified' in a good way?? If so, I guess I would have used a different term that didn't have such a negative connotation.

Re:Racket: The Lisp for the Modern Day by wartijn_ on Thursday June 29, 2023 @10:18AM (#36520679)
Re:Racket: The Lisp for the Modern Day by fulafel on Thursday June 29, 2023 @10:31AM (#36520857)
I think being conservative about evolving the language, and ecosystem growth are mostly different issues, the open source post was about the core language.

Comparing to other languages I think the stability of the language has served the user community really well and been an enabler of the ecosystem. I guess the continuous language additions and resulting complexity & library/framework chuirn in some otherlanguages can also be seen as vitality and growth, but for many of us it's the wrong kind of growth.

(And yes there are also disadvantages to the centralised development model of the core language)

Re:Racket: The Lisp for the Modern Day by waffletower on Thursday June 29, 2023 @11:17AM (#36521553)
The iron grip is on a decidedly double-edged sword. I applaud the continuity and maintainability of Clojure and its ecosystem. The consistency of the language has come from this stern stewardship. Rich makes very clear that the source code for the language is available to be forked. Very interesting developments have come from this, most notably babashka.