4 ms·
In my experience, the old tools are generally rock solid and are still viable—deps.edn is where a lot of the momentum is going, but Leiningen still works as wel
by actuallyalys 4y ago
In my experience, the old tools are generally rock solid and are still viable—deps.edn is where a lot of the momentum is going, but Leiningen still works as well as ever. I haven't actually tried to create a new project from an old template recently, but projects I created with old template still run fine.
The big exception is ClojureScript. I haven't personally noticed bitrot as much as ClojureScript being generally flaky. I think the situation is improving, though, and the unreliability is mostly in compilation and hot-reloading, not at runtime.
I think Clojure could use more funding to improve tooling, but I do think we have made strides with the funding we have.
- synthc 4y agoI feel your pain regarding ClojureScript. A few years back there was a 3 month window where I had everything (lein,fighweel, emacs) configured just right, and I could reliably start a Clojure REPL, a Clojure Script REPL connected to a browser window, and switch between them from emacs. It was really productive, I could work on the backend parts, frontend parts, and effortly switch between REPLS, but then there were some updates and I never got it working without friction again.
- pyb 4y agoThis is the same setup also I've been failing to reproduce.