Hacker News new | ask | show | jobs
by divtxt 5432 days ago
The java classes have always had major warts and no one in charge has ever seemed to care.

My personal bugbear: java.lang.Object depends on hundreds of classes including, among other absurdities, the Turkish locale (IIRC). This was about 13 years ago. Of course, the bug was eventually marked WONTFIX.

14 years ago, I adopted Java because it was a beautiful escape from the warty giant that C++ was becoming. Sun sat on it's laurels and, like many others, I moved on to Python.

Now Java is the new C++: unpleasant and to be avoided when possible.

1 comments

Could you elaborate?
Sorry for the late reply. Not sure which you wanted details on:

- java issues / sun not caring - there are examples above by SeanLuke, gojomo and myself

- java.lang.Object depends on hundreds of classes - violates basic design principles of modularity and avoiding cyclic dependencies

- "Sun sat on it's laurels..." - apart from ignoring existing issues, they also ignored requests for language enhancements (e.g. dynamic language support, covariance, etc) for a long time causing many developers to give up on java for web development and move to python & ruby