[uxcolumbo]

Not sure this type of response helps and referring to someone who is active in the Clojure community and tries to build some cutting edge stuff as 'this guy'. (Did some digging and hyperfiddle looks pretty cool).

I think it would help to understand why he is talking about this 'every two months' and then try to address his concerns.

Would be a shame to lose people who are active in the community but not heard.

[lgrapenthin]

Of course calling out baseless FUD is helpful. Otherwise it just discourages people from engaging with Clojure, which is not helpful.

[uxcolumbo]

Of course. But for people not in the know and looking outside in, they don't know what's going, i.e. why is someone who's been using Clojure for years and building a business with it making these points every few months as you say?

To counteract FUD it would be useful to give a few more details.

[lgrapenthin]

Might be some personal beef, but I don't know really and don't care enough. He makes these authorative claims mixed with personal sentiment and then doesn't back them up.

Here for instance the core team supposedly has "lost control of the compiler" https://x.com/dustingetz/status/1947643515480965346

Work on the compiler had been pushed a month earlier https://github.com/clojure/clojure/commit/6a3e0f02c6a96fcef2...

[uxcolumbo]

Thanks for that. These details are important for newcomers, because it seems the original commenter isn't happy with the core team's process and 'feels like it's falling apart' is hyperbole and subjective.

For future readers: Clojure is known to be extremely stable and backwards compatible. It doesn't suffer from the same churn, fatigue and breaking changes that the JavaScript ecosystems experiences for example. To get to that backwards compatibility it requires a different process.