News for hackers. Stuff that matters.
Re:Lessons learned after working one year as a Common Lisp D... by iostream23 on Friday December 10, 2021 @03:40AM (#29507772)
Except we just brought the JVM onboard, with its own headaches. The JVM is arguably as much of an obstacle to developing solutions as boilerplate in Java. You end up having to debug obscure JVM errors in production instead of sticking to Clojure. It’s also not doing any of the compiler tricks CL and schemes are noted for.
Re:Lessons learned after working one year as a Common Lisp D... by kaba0 on Friday December 10, 2021 @05:13AM (#29508301)
What obscure JVM errors do you talk about? I’ve never ever had a JVM bug and while I don’t have decades of experience, I didn’t start today either. The JVM is hands down the easiest to debug platform, where you can connect to a prod instance remotely and see basically everything. Clojure does have a few not too readable errors, but I think that’s on Clojure’s semantics, has nothing to do with the JVM.
Re:Lessons learned after working one year as a Common Lisp D... by simongray on Friday December 10, 2021 @03:52AM (#29507840)
There is no silver bullet. Clojure is a great set of trade-offs.