4 ms·
As an engineer that last used Java when it was Java 11, I cringe at the thought of diving back in. A trade-off of increased release velocity for any language I
by digitalsanctum 4y ago
As an engineer that last used Java when it was Java 11, I cringe at the thought of diving back in. A trade-off of increased release velocity for any language I suppose.
- kaba0 4y agoWhy? Only the encapsulation difference was a slightly bigger breaking change since 8, after you are done with that it really is smooth sailing. Or if you mean addition of new features, then Java is very conservative on that front and it is still a very small language compared to most other mainstream ones.
- nprateem 4y agoIt's really not as bad as it used to be. I recently picked it up again after playing with Spring boot. I got to say Spring boot seems awesome, and java as a whole it much more ergonomic. Worth another look.
- twblalock 4y agoYou don’t need to learn or use any of the new features. Most devs seem to still pretend they are writing for Java 8 anyway.
- oulu2006 4y agoI use Clojure, which benefits from these consistent JVM improvements; things like pattern matching have been accessible to me for years already, but I like that Java slowly trails along as it helps keep me vested in the Java ecosystem.
- cutler 4y agoBy contrast I despair of Clojure ever keeping pace with Java updates. Clojure seems to be a functional language which isn't even implemented using the host's functional features which were introduced 9 years ago.
- oulu2006 4y agoI guess that only matters if we're missing out on performance improvements by not using native language features; be cool to see if anyone has done any profiling/investigation on that. Clojure the language isn't missing anything I need.
- yCombLinks 4y agoNearly all of the language changes except for the thread changes are minor quality of life things.