4 ms·
Java has reached the status of Cobol - it is immortal because it is everywhere and has been around a long time. Because of that, there are a lot of Java devs.
by tomohawk 4y ago
Java has reached the status of Cobol - it is immortal because it is everywhere and has been around a long time.
Because of that, there are a lot of Java devs.
Our team works in Go, and so we get a few Java devs in once in a while as new positions open up. The biggest change for them is to get out of archonaut mode and stop overdesigning everything. After going through a 3-6 month cleanse, it's fun to see them complain about the legacy Java stuff and how overly complicated it is and how slow it is to build and test compared to Go.
- ralmidani 4y agoWe use Elixir at work, but a lot of us either did a Java bootcamp, or came over from Java jobs, and in some places the codebase reflects that. I love your use of the word “cleanse”.
- kaba0 4y agoThat’s funny because Go is much less expressive than even Java. If anything, their overdesign seems to come from their juniority and badly ingrained “best-practices”, nothing inherent in the language.
- al_mandi 4y agoHaving used both at different employers, I agree. The golang code I've seen was much worse on almost every level than other code I've seen.
- SureshG 4y agoModern java (check this - https://www.infoq.com/articles/data-oriented-programming-java/ https://www.infoq.com/articles/data-oriented-programming-jav...) is really not that bad. Golang is like far more verbose than even JDK 8 (9 old release) for most parts. The issue is, many java users have only experience with spring ecosystem for doing most of the stuffs. There are far better alternatives in java ecosystem. There are other JVM languages like Kotlin with provides 100% interop with the ecosystems and is far better language than go.
- peterashford 4y agoHmm... I'm using go commercially now for the first time and I thought it was pretty wordy. Especially in error handling.