Re: What's bad in Java
- From: Evans <onyxtic@xxxxxxxxx>
- Date: Sat, 31 May 2008 14:14:57 -0700 (PDT)
On May 31, 10:08 pm, Jack <j...@xxxxxxxxxxx> wrote:
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.
In as much as I use Java as my main development language, I also
develop in Python. In fact, I've been very happy using it in the last
6 years and have no complains whatsoever.
If you'd like to try out a very expressive and sexy language, then do
yourself a favour and try Python.
Evans
http://www.jroller.com/evans/entry/concurrency_and_performance
.
- References:
- What's bad in Java
- From: Jack
- Re: What's bad in Java
- From: Lew
- Re: What's bad in Java
- From: Jack
- What's bad in Java
- Prev by Date: Re: Using POST to send bitmap image with Java
- Previous by thread: Re: What's bad in Java
- Next by thread: Re: What's bad in Java
- Index(es):
Relevant Pages
|
