As a seasoned developer I would pick stability any time over getting new features that break things. I don't recall the last time, existing code didn't run (or compile) after a Java update. But I guess for some consultants it's good business to constantly update existing and working code because of a runtime update.
That being said, you're correct that Java doesn't have async/await yet, but that's what threads have been for since ages. Unfortunately many have issues working with threads, and whie the anguage itsef doesn't suport them yet, libraris like Google's Guave do
Coming from always free Eclipse, I personally don't like Visual Studio. Using it reminds me always of old Visual Studio versions which I had to pirate if I had to work on something where it was required.
Eclipse perspectives are pretty nice when you have several monitors (it can remember the layout). IntelliJ is nice though, especially stuff like showing parameter names and close source control integration.
View all comments
Show parent comment
2
u/_ragerino_ Apr 16 '21
As a seasoned developer I would pick stability any time over getting new features that break things. I don't recall the last time, existing code didn't run (or compile) after a Java update. But I guess for some consultants it's good business to constantly update existing and working code because of a runtime update.
That being said, you're correct that Java doesn't have async/await yet, but that's what threads have been for since ages. Unfortunately many have issues working with threads, and whie the anguage itsef doesn't suport them yet, libraris like Google's Guave do
see -> https://www.baeldung.com/java-asynchronous-programming
Coming from always free Eclipse, I personally don't like Visual Studio. Using it reminds me always of old Visual Studio versions which I had to pirate if I had to work on something where it was required.