What parts of Java do you dislike and why?

[Petr]

Hi everyone.

Recently I looked some ads about Java vacancy and found this question and really I have doubt with this. I actually don't know how to answer on this question.
So What do you think about it? Any suggestion. :)

Regard.

[KevinWorkman]

Honestly? I dislike questions like this.

But if I were to give an answer, it would be the misconceptions around the language. People think that Java is slow because when it was first being used, programmers didn't know how to use it- they did things like put a bunch of work on the EDT, which caused the program to become unresponsive. That didn't mean Java was slow, it meant that the programmer was using it incorrectly. Couple that with the metrics for the original JRE being "slower" than equivalent languages (not that the difference really mattered to 97% of programmers or users), and people who know nothing about Java or programming still tout "Java is slow!" even though it's simply not true. For more information: Java performance - Wikipedia, the free encyclopedia

The other misconception is that Java programs are all ugly, gray, square buttons used for boring business software. Sure, that's ONE application of Java (and many other languages), but one look at the featured board at JGO should shut anyone up about Java not being cool/beautiful/game-worthy.

Other misconceptions are things like "teh Jav is dead", which is, again, simply not true.

[JosAH]

I personally dislike the explicit boolean type; I prefer it the 'C way': anything not 0, 0.0 or null is considered true. But that's just me ...

kind regards,

Jos

[Petr]

KevinWorkman Thanks for your opinion, but I want to hear your opinion about this questions. You just pointed peoples opinions who don't use Java in job as profession developer. for example JosAH said good thing. Sometimes I get bug in this cause like this;

Integer i = null;
passParams(i);
....
void passParams(int value) {

It will be compilated but it is not run. because primitive type must be not null in Java.

[KevinWorkman]

KevinWorkman Thanks for your opinion, but I want to hear your opinion about this questions. You just pointed peoples opinions who don't use Java in job as profession developer. for example JosAH said good thing.

I'm not sure what use you think this information would be to you. Different languages are useful for different things. The people here obviously find Java useful for most things, or else they wouldn't be here. So you aren't going to get a ton of responses. My answer isn't just about people who don't use Java- it affects people who do, as well. For example, management might hear from somebody that Java is slow and decide not to use it, even though it's the best tool for the job. This is a real downside of the language, in that it's underrated and undervalued, at least some of the time, so as a developer of Java I sometimes feel the same way.

Sometimes I get bug in this cause like this;

Integer i = null;
passParams(i);
....
void passParams(int value) {

It will be compilated but it is not run. because primitive type must be not null in Java.

I don't want to be too pedantic, but that's not a bug, and it is run, and that's not the reason you get the Exception.

[couling]

I personally LOVE the strict typing of java.
The fact that it will not implicitly cast from int to bool stops 90% of "if (x = y)" coding errors before the program will compile. Actually the "=" for assignment is a minor negative but its conventional so I don't notice it.

For me the worst point of java is that in order to make all code portable, there is no support for some (frankly very common) os features. Unix sockets spring to mind. This makes it impossible for java to interface with some programs without diving into JNI. I've had to re-configure my PostgreSQL server just to allow Java to connect. I've then had to implement an Ident server capable of translating between IPV6 and IPV4 just to get java to authenticate with PostgreSQL based on O/S user.

And yes the performance is an issue... For larger programs not so much. But with small command line programs; the time it takes for the JVM to initialize can be many times the entire runtime of an equivalent C program, making small light weight java programs rather slow.