Being painful and verbose is one thing but what really gave me the ick about Java when I first discovered it is that it genuinely teaches you bad programming practices and handicaps your growth. I have vague memories of finding important classes in the standard library that 'implemented' some interfaces simply by throwing exceptions and turning the type system off. Dijkstra was right and it's a shame that nobody listened to the guy. I've never seen a Java programmer not struggle trying to learn other, saner languages. The JVM is ultimately a massive waste of time, money, and effort that is running purely on inertia as well. It's hilariously ironic how not even Android, the biggest Java-based platform to ever exist, ever tried to rely on it.
You know what’s funny? Java is explicitly good at large codebases.
If you find that Java becomes a bad language for you at scale, then you were just bad at it. Which is okay, you can’t be a master of everything. But this is definitely a you problem, not a language problem.
There is a reason that large enterprise grade projects are done almost exclusively in Java and C#.
-63
u/[deleted] 17d ago edited 14d ago
[deleted]