Not a Python fan (like, at all) but can't say I'm surprised. I'm doing still lots of Java development as freelancer to pay the bills, but the Java9+ "update" has just deprecated too much of the Java ecosystem. World-class backward compat was the one thing that Java got right, but lifting a couple years old Java apps to Java 8 and 9 was such a painful experience (with Spring 3->4, idiotic deprecated "REST" frameworks, and old netty servlet and jspc maven conflicts, none of which had a reason to exist in the first place IMO). Ironically, as we're moving to a world of closed language ecosystems, and nobody produces regular shared or static libs anymore in favor of the respective language's own little package manager, the Java ecosystem could have played to Java's strength. It's depressing to loose a whole generation's work of love who saw Java as the go-to language for such a long time with two world-class IDEs to choose from, but I guess Java has run its course as a language that started as a bytecode format for set-top boxes. Will Python (started as the ABC language for non-technical users) take its place? I highly doubt it.
Update: do you have a recommendation for a Java exit strategy? Like, using a language that can compile to JVM byte codes to integrate with existing code bases, yet can also be compiled into native code on x86/64 and ARM/64 for linking against?
Update: do you have a recommendation for a Java exit strategy? Like, using a language that can compile to JVM byte codes to integrate with existing code bases, yet can also be compiled into native code on x86/64 and ARM/64 for linking against?