> A boring codebase doesn't make a bored developer, on the contrary it frees developers up to think about important stuff and deliver value to the business. Just as I want my language to be boring so I can focus on interesting stuff, I also want my tech stack to be boring - the interesting bits should be in the value added, not the stuff under that.
This. I don't want to work with niche languages anymore, and artisanal, hand-crafted in-house libraries/frameworks.
I want to use boring shit like the JVM or the CLR (.NET) and the libraries with the most answers on Stackoverflow so that things "Just work", issues are debuggable, the authoring experience in my IDE is solid, and I can use what little braincells I have to focus on building features + solving problems.
Niche languages and wacky libraries are for my weekend projects + personal fun-time.
To be fair, they didn't say Java, they said JVM. That allows Kotlin, Scala, whatever.
Java is missing so much and has so many design errors (which are acknowledged as errors), I agree that it should be avoided.
I think Rust is a better language, but you can't exactly incrementally convert your Java codebase into Rust very easily. If you stay in the JVM, things like that are much easier.
Care to explain why? I get that there are some horrible Java projects and libraries that have really ballooned in complexity over the years but I still see Java itself as one of the better languages. Especially for corporate work.
I want to use boring shit like the JVM or the CLR (.NET) and the libraries with the most answers on Stackoverflow so that things "Just work", issues are debuggable, the authoring experience in my IDE is solid, and I can use what little braincells I have to focus on building features + solving problems.
Niche languages and wacky libraries are for my weekend projects + personal fun-time.