Re: What's bad in Java

Lew a écrit :
> [a bunch of points]

It won't. First of all, it's clear your goal is to flame, and I doubt anyone inventing Java cares much about that. Secondly, you haven't really expressed anything concrete that can be addressed. Things that are changing in Java, such as speed (at which Java has for some time been roughly even with other languages like C or C++) and GC, are being handled in ways that seem quite effective. A couple of your comments, like "[t]he difference between checked and unchecked exception[s]", don't even express a criticism, so there's nothing for the Java mavens to address.

Java is far from a perfect language or platform, but the valid criticisms are pretty specific and technical. Words like "dumb" and "ridiculously" don't give much handle for productive resolution. Recast in technical terms, with precise terminology, and for Goddess's sake study the reasons why things are the way they are before you start taking shots at them. Be careful when presenting a laundry list like this; get one thing stupidly wrong and you will cast aspersion on the validity of all your points, even if some of them are worthy. If you convince people that you are a trollish putz, they will ignore even your best advice.

Thanks for reading. People who thinks its a trollish putz are wrong. My aim was to see what other Java programmers might think about my points. I think if nobody agrees about what are the problems in Java, the language/JDK will never change. If it does not change, i hope another programming language, some kind of sequel will replace it, with these problems fixed. I hope that a lot...

I'm coding in Java for 3 years now, and i'm pretty sure that i'm right about my points. They are concise ways of expressing my everyday problems with Java, so i don't get you.

The guy who will say to me that using the Java ArrayList<Integer> is as fast as using int[] in C is a liar. I just don't understand why people want to believe Java is not slow. IT IS !!! It is because nobody write Java code using C style primitive type.

I won't talk about memory, i think it's obvious.

Anyway, if somebody can give me hint on a programming language which fixes the listed problems, well i would be glad.

And my last point will be that some language (like C# i think) offers a solution to some points (the accessors), so i think i'm not the only one to find writing accessors dumb.
.

Relevant Pages

  • Re: Symbol Grounding Problem
    ... particular programming language at all. ... powerful" than Java. ... I didn't directly address the question of comparing Lisp and Java. ... what does one mean by "powerful" in a programming language? ...
    (comp.ai.philosophy)
  • Re: Comparing Lisp conditions to Java Exceptions
    ... All the ISO standards in the world will not make the world ... Nothing keeps you from annotating your program with exceptions based on what ... language should adhere to your theory. ... Curiously, although you don't say it, Java has the opposite problem. ...
    (comp.lang.lisp)
  • Re: Controlling Internet Explorer from a java application, the SHDocVw.InternetExplorer object or so
    ... Java is a programming language. ...
    (comp.lang.java.programmer)
  • Re: casts
    ... This is why most shit programmers refuse to learn languages including ... C Sharp and Java. ... compiler in a later edition of Visual Basic, ... language for processing data. ...
    (comp.lang.c)
  • Re: [Full-Disclosure] automated vulnerability testing
    ... No language is secure unless you ... There is "the Java runtime environment" (which is pretty much ... inherently secure by design) and "the Java programming language" (which ...
    (Full-Disclosure)