NHacker Next
- new
- past
- show
- ask
- show
- jobs
- submit
login
Rendered at 23:26:43 GMT+0000 (Coordinated Universal Time) with Vercel.
Very cool!
I think the aot compilation story on the JVM lacks fast tooling with good UX compared to go.
And Clojure is legitimately good at data processing.
The MCP server is a relatively simple project, don’t think that’s a bad idea.
You realize that the term "AI" didn't come to life in 2009, it's been around for over 70 years?
The Clojure community is very mature and incredibly nice, so things are not bad as they are, but they could definitely be better.
I try to set aside a portion of my business revenue (I call it a "sustainability fee" in my P&L) and spread it among the authors of libraries that I use. It's not much for each author, but if everybody did this, many authors could work on open source libraries full time.
Clojure is the most stable and robust language I've ever used, and I've been using it in production for 15 years now.
Doesn't that mean the core developers are now funded by NuBank?
Isn't it in their interest that 'the core language (Clojure and Clojurescript) to not feel like it is falling apart'?
And what do you mean with falling apart?
I'm new to Clojure, so the above is a genuine question.
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.
To counteract FUD it would be useful to give a few more details.
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...
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.
The downside of that is it's slow and difficult to get changes in
Instead of talking about throwing money to get the contributors to fix what you want it would be better to publicly talk about the problems
Are they tracked or known, what do they stop you from doing, how long have they been in the queue have you had any feedback etc?