But there was a period when Java paid the bills, so I got proficient at it. Jumped ship as soon as I was able to.
I still don't know if there's any other language with that amount of "ceremonial syntax" out there.
But there was a period when Java paid the bills, so I got proficient at it. Jumped ship as soon as I was able to.
I still don't know if there's any other language with that amount of "ceremonial syntax" out there.
As annoying as Java is, please don't mistake pattern over-engineering with the language. One could choose to do the same things in any OO language, like C# or C++. And as someone pointed out here, there are similar obscenities in the FP world, they are just obscured under higher-kinded types and algebras.
... although you alluded to one problem that Java has. Its frameworks were developed during the height of design patterns and many (like Spring) are bloated or overly complex or not worth the trouble (and actually, I think design patterns, when used very carefully and in truly useful situations, can be fantastic).
Yeah, actually, I like Java (it gives application devs just the right amount of control) and think to save it, needs to purge itself of Spring.
But in practice "FactoryFactoryFactory" (*) is commonplace across codebases, frameworks, libraries, etc.
Java in the real world doesn't happen in vacuum.
(*) I know it's an extreme example, just kind of trying to make a point succinctly
Using a modern Java framework would have been such a superior approach. And it's even better now with records, pattern matching, virtual threads, and string templates (in preview).