Been coding in Java since the late 90s. Honestly I have a love-hate relationship with it. On the one hand, it's a known quantity, reliable, and stable. I don't

Been coding in Java since the late 90s. Honestly I have a love-hate relationship with it. On the one hand, it's a known quantity, reliable, and stable. I don't mean this in a negative way. With so much industry churn, Java has done amazingly well. I'm liking the language updates as well, since Oracle took over especially so, which surprised me a lot to be honest. Interfaces like JDBC are really underrated. When using Node or Rust, I can't help but notice how almost every database driver has a separate and incompatible API. I honestly think Java hit the sweet spot with naming conventions. At a glance I can tell when something is a property, a method, a class/interface name, a static member, or a constant. Java also deserves credit for popularizing dynamically-generated documentation in Javadoc. To be honest, I only have a few complaints. It's more than fast enough, but it's still the biggest memory hog by far among the most popular languages. The tendency for Java programmers to rely on inheritance too much irks me. And nulls. Oh, the nulls. I've been finding myself writing Java more like Rust lately where I don't return nulls from methods anymore if I can help it. Optionals or empty collections, but never null. I really wish Java had followed this model from the start, but hindsight is always 20/20.