3 ms·
If you want to avoid Java just for those naming styles, while the ecosystem is actually great (doc, tooling and lib maturity) you’re doing it wrong. Java works
by alanfranz 3y ago
If you want to avoid Java just for those naming styles, while the ecosystem is actually great (doc, tooling and lib maturity) you’re doing it wrong.
Java works. Its effectiveness is high, and it’s quite uncommon to hit rough edges since it’s so well tested. A smooth ride forbackend when compared to languages like Python or Javascript.
- artyom 3y agoI kindly disagree. Python tooling, documentation and lib maturity is nowadays comparable to Java IMHO. Which one is better suited for your problem is a matter of perception. Javascript (on the backend) is obviously a different story.
- ssijak 3y agoTooling for a dynamically typed language can never be on the same level as for a statically typed language. And among statically typed ones, from my experience, Java/JVM has the best and most mature tooling by far.
- EdwardDiego 3y ago> Python tooling, documentation and lib maturity is nowadays comparable to Java IMHO. Having moved to a Python shop, I disagree. I really would like it to be true, but it's not.
- peterashford 3y agoHaving just recently moved on from a Python shop, I have to disagree. Vehemently. Python tooling is in no way as good as Java's.
- jmopp 3y agoI feel like Java was designed in a way that runs contrary to how my mind works. I tend to navigate code starting at the entry-point and going deep. With lots of layers of abstraction, it's hard to figure out what is actually being run, and I tend to get lost in a Java codebase.