3 ms·
It’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
by erik_seaberg 3y ago
It’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.