News for hackers. Stuff that matters.
Re:Clojure 15th Anniversary: A Retrospective by jimbokun on Saturday October 22, 2022 @09:45AM (#33298254)
> 1. No framework. Clojurists tend to prefer libraries and I would too, but for a newbie starting out, when every other language seems to have converged on one standard way of doing things (Spring, Rails, Phoenix, Django etc), Clojure just gets in the way with decision fatigue.

As someone who codes professionally with Spring frameworks every day, this is a huge selling point for Clojure to me!

It is such a huge, opaque, convoluted, complex unpredictable mass of code, that forces broad changes to working code whenever you upgrade to a new major version.

One of my favorite Spring debugging anecdotes was where a coworker was trying to find a class from a runtime stack trace in the libraries. Only to discover that the class didn't exist in the source at all, but was dynamically generated by Spring at runtime!

Your other points I largely agree with.

Re:Clojure 15th Anniversary: A Retrospective by kaba0 on Saturday October 22, 2022 @01:03PM (#33300037)
> Only to discover that the class didn't exist in the source at all, but was dynamically generated by Spring at runtime!

With all due respect, that’s like numero 0 thing to know about Spring’s AOP which is like the second most important part of Spring after dependency injection.

Re:Clojure 15th Anniversary: A Retrospective by jimbokun on Monday October 24, 2022 @12:52PM (#33319161)
Yes, and that's not a good thing.

It breaks down the fundamental debugging model of looking up the code in stack traces and seeing what it does. When an exception is thrown in generated code, what do you do to debug it?