| |
| ▲ | seancorfield 2 hours ago | parent | next [-] | | Clojure 1.9: Spec. Clojure 1.10: datafy/nav + tap> which has spawned a whole new set of tooling for exploring data. Clojure 1.11: portable math (clojure.math, which also works on ClojureScript). Clojure 1.12: huge improvements in Java interop. And, yes, the new CLI and deps.edn, and tools.build to support "builds as programs". | | |
| ▲ | vaylian an hour ago | parent | next [-] | | And we can look forward to Jank https://jank-lang.org/ | |
| ▲ | whalesalad 2 hours ago | parent | prev [-] | | Things have surely happened and the language has improved, but would you consider any of this to be innovative? | | |
| ▲ | jwr an hour ago | parent | next [-] | | Hmm. I'm not sure what you are looking for — myself, I write software that supports my living, and I'm not looking for thrills. What I get with Clojure is new concepts every couple of years or so, thought through and carefully implemented by people much smarter than me, in a way that doesn't break anything. This lets me concentrate on my work and deliver said software that supports my living. And pay the bills. | |
| ▲ | waffletower 39 minutes ago | parent | prev [-] | | Babashka is definitely innovative and useful |
|
| |
| ▲ | iLemming 2 hours ago | parent | prev [-] | | > zero innovation has occurred in the Clojure space since 2016. Oh, really? Zero, eh? clojure.spec, deps.edn, Babashka, nbb, tap>, requiring-resolve, add-libs, method values, interop improvements, Malli, Polylith, Portal, Clerk, hyperfiddle/electric, SCI, flowstorm ... Maybe you should've started the sentence with "I stopped paying attention in 2016..."? |
|
