3 ms·

I really think they are "trading off stability for shiny features" Oracle wanted money from google for using java to create google search and creating Android.

I really think they are "trading off stability for shiny features" Oracle wanted money from google for using java to create google search and creating Android. Didnt get any, and now they are trying to attract devs who are starting similar ground breaking ideas on go and rust with a similar disregard for robust failure states and long term code viability which is always what separated java from its competitors. Why else depreciate all the features that made it perfect for huge teams building systems that never broke and adding "things rust, go and v8 did"? as for the test suite, not touched java 17, looking at the "whats new" the main thing I can say for sure is "new" is all the security manager stuff that wraps code made by 3rd parties is going to be marked with depreciated, but no clear upgrade path.

sandGorgon 5y ago
look - the tradeoff here is large vs large. I detect a certain disdain for Android - however there is probably a larger dev pool right now who want that (versus you). I dont disrespect your usecase, but any company would have to service its largest market first. And if the largest markets are all Android, Spring Boot, Kafka, Spark, etc... then that's where they will go. I have been in your situation, but ultimately this is a Python 2 vs Python 3 situation. If you want to stay on Python 2..then you better be able to maintain it yourself. Its just a larger pool of users on the other side. And this is the common developer on the street wanting to use Kotlin, Clojure, etc. This is the market, so here we are.