Speaking of editions, wasn't there a hint, perhaps of a 2nd edition of Clojure Applied? Did I get that wrong?

This has probably been discussed before but what do you think are the benefits of the JVM and Java ecosystem of libraries? Given how widespread java is I can’t easily find any modern advocacy for it beside the really shallow link-spam present everywhere

@dimitar.ouzounoff The main benefits for me are the millions(?) of engineer-hours that have gone into all of that to make it stable and fast and provide a very, very rich set of robust libraries for pretty much any task. Plus, the JVM runs "anywhere" so I only have to target one platform.

I've been working almost exclusively on the JVM for over two decades at this point, using about half a dozen different languages -- and the interop between those languages is another thing the platform provides.

Things are containerized now so JVM value prop is a lot weaker than 10-15 years ago but i think the JVM observability tools still apply in scaled up clojure deployments; also ClojureScript remains a huge value prop; and code-sharing between different platform components of a larger cloud system (e.g. client/server/db) is an underutilized value prop that is a game changer for future cloud architectures

Something that comes to mind is that Kafka interop is trivial with Clojure but using it from Ruby or JS one feels like a second-class citizen, C interop or whatever was powering those was definitely frustrating (Probably there's a more generalized principle that can be extracted from my anecdata)

Based on the other ecosystems I've tried, there are few alternatives that provide the breadth and depth you can find on the jvm. In no particular order: • Strong support for concurrency and multi-threading • multiple programming languages • cross platform • performance. JVM langs are generally competitive or faster than many of the other popular high-level langs. • libraries for complex, existing technologies. This list is huge. Some examples: IMAP, Microsoft Office doc reading/writing, database integration, IRC, SMTP, crypto, PDF, etc. These are the kind of things that can be very difficult to build yourself. • Most new technologies ship with libraries for the JVM very early on. If there's a new cool database or magic cloud thingamajig, it will probably have a Java SDK. • Strong support for native integration: JNI, JNA • LTS support for the foreseeable future • Graalvm is adding new capabilities for compiling to native that cater to even more use cases • established, mature tooling for profiling, debugging, deploying

https://twitter.com/richhickey/status/1261294338585346053