4 ms·
In terms of a culture of over-engineering, yes, it is second to none. In Java land, even a logging library can be a serious security vulnerability. A typical Ja
by grumpyprole 5y ago
In terms of a culture of over-engineering, yes, it is second to none. In Java land, even a logging library can be a serious security vulnerability. A typical Java project pulls in half the internet for dependencies, including multiple logging libraries.
Java is therefore somewhat a victim of its own success. There is no absolute "best" as you seem to suggest. Every ecosystem has pros and cons.
- hkt 5y ago> A typical Java project pulls in half the internet for dependencies, including multiple logging libraries. Rationalising a language's ecosystem is harder than building one. I suspect that this drives at least some new language adoption.
- azth 5y agoSounds like FUD
- grumpyprole 5y agoI've done years of Java dev at many large corporates, so there's no uncertainty. Plenty of fear and doubt though. The language is getting much better, let's hope the ecosystem does too.
- azth 5y agoAny language at a large corporation (without proper software engineering practices) would end up that way. My current employer uses golang, and you wouldn't believe the @)%(* they came up with. Such as an entire framework that spits out 80+ line stack traces for errors and panics.