Link Details

Link 84227 thumbnail
User 246188 avatar

By kbilsted
via bluej.org
Published: Jun 01 2008 / 07:12

Great article about the problems of an ever increasing complexity in Java at the cost of readability and understandability of the code - especially for newcommers to the language. The article is well written, and argues well for its points. It's main point should be included in discussions on the future of Java...
  • 15
  • 3
  • 1886
  • 613

Comments

Add your comment
User 270877 avatar

killerweb replied ago:

1 votes Vote down Vote up Reply

First off Java has simplicity already and has had it since 1995, thats the problem. The so called language masters didn't want to add in anything to the language for such a long time. That's why today we have such bullshit code like getXX and setXX and not true components. We've been hacking it for so long we forgot what "simple properties" look like. And that's just one example. You first have to have bloat to say can it survive it! Java is far from bloated, so far as to say, Java the language is actually THIN! But the platform libraries are not because of this very reason of a THIN language. So much code is verbose because of the lack of language features. I think the bigger problem is the choices of things that are added. Like Annotations! WTF is that about. You add one new feature and its the be all feature, all new specs and code uses annotations like its the savor of the language. And again it's a freaken hack just like getXX and setXX. Simplicity for Java can be summed up as, "what's the smallest thing we can add to Java that gives the language the largest bang-for-the-buck". So Closures, Properties and fix the freaken Generics spec, and I for one will be happy for at least the next couple years. I'm sure every developer has the "wish list" going for them.

User 246188 avatar

kbilsted replied ago:

2 votes Vote down Vote up Reply

I think there is something wrong in Java-land. I think this article was well written although it sort of goes against my wishes to see new stuff in the language to do things smarter..thus my vote UP!

User 131196 avatar

Jakob Jenkov replied ago:

0 votes Vote down Vote up Reply

I want unsigned pritimtive types. Bit manipulation is totally ugly and annoying using the signed primitives.
Give me ubyte, ushort, uint, ulong, and I'll be happier. I can't think of a single reason why those types
weren't added from the beginning.

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.