3 ms·
The JVM’s main value props are a world-class single dispatch runtime and GC, and a huge ecosystem of compatible OO libraries. It also doesn’t care whether you a
by erik_seaberg 3y ago
The JVM’s main value props are a world-class single dispatch runtime and GC, and a huge ecosystem of compatible OO libraries. It also doesn’t care whether you are writing Java by hand. If your team can master any of the more concise and productive languages, they should.
- pjmlp 3y agoExcept the tiny detail that a big part of that value proposition is written in Java. If people want to ignoring the foundations of their toolbox, that says a lot about the skillset.
- erik_seaberg 3y agoIt’s hard for me to judge, when I’ve known Java since 1996. I might need to know Java, but I don’t need to write it. Maybe it’s enough that someone on the team knows it. Maybe it’s not really possible to master Scala/Clojure/Kotlin/Groovy/AspectJ without knowing at least some Java. Likewise, I probably need to know C to use POSIX, but it’s so unsafe that I should not be writing it.
- pjmlp 3y agoYes, the poor guy that needs to jump in for: - understanding stack traces - writing idiomatic bindings for libraries - debugging why Java frameworks fail consuming jar files whose bytecode was generated in a different way - debugging why a jar misbehaves after a JVM bytecode rewriting tool messed up the bytecode sequence used to emulate other language semantics on top of the JVM - adopting libraries whose compiler plugins and annotation procesors only understand Java semantics - mapping debuging information and telemetry data from tooling like JFR into the original code of the guest language.