vuurrobins devblog

I have been working with java for quite some time now, and the more I look at it, the more I dislike it. It has some good design decisions that it implements well, it has some good design decisions that it just didn’t implement well, and there are some design decisions that just made me go WTF. Now I know that some of those decisions are because they thought that it was the best way back when they created java (the language is 15 years old, being first released in 1995) or trying to make the language simple and idiot proof or that the decision was based on another, older decision to keep compatibility between java versions. But that doesn’t mean that the decisions aren’t bad. So here are 7 design decisions that I think are either bad or badly implemented.

Note that I only list things of the core language here, not of the standard library, frameworks/libraries, documentation, virtual machine, etc. I also try to be objective and put only actual decisions here without going into a rant. Although I don’t explicitly say what it should be, I think that it is fairly obvious to tell what needs to be changed to improve the language (although that would change the language to much). I also make a lot of comparisons with c++ because I have the most experience in it and I like the most.

One final thing before we go to the list. This is just my opinion. If you disagree with me and you want to discuss it, then go ahead, but do it in a respectable fashion or go away. There are a lot of other people’s opinions that you can read.

On to the list:

(more…)

I’m currently busy with creating the DSOL code for reading key presses, and I’ve run into some interesting stuff (I think) about how to create read only class variables.
(more…)