of course java is evolved, new functions are added in new version:
template class, annotiations, class boxing of primitive types... but C+
+ is always more complex! java has not pointers, you don't have two
notations "." and "->", you don't have destroy objects, exception
handling is more simplex; java is avoid from overflow error, and at
the end there is more documentation!

Awwww.  Can I get you a tissue?

I don't find Java as a language to be much more complex for its evolution,
but I do find it being used to build systems and architectures that are much
more complex than those from 10 years ago.  Generally I think that's a good
thing.

Matt Humphrey matth@ivizNOSPAM.com http://www.iviz.com/

You don't have to use fancy pants new libraries.

class worlds_smallest_violin{
 private boolean play=false;
 private String song="";
 public worlds_smallest_violin(String song){
     this.song=song;
 }

 public void play(){
   System.out.println("I'm playing the "+song);
 }

 public static void main(String args[]){
   worlds_smallest_violin wsv=new worlds_smallest_violin("World's
Saddest Song.");
   wsv.play();
 }
}

I mean you can still get a simple hello world program up and going
that easily,

Ben.

Most of the stuff added to Java was added by popular demand, to support more
complex applications. I think it is inevitable. Most of the stuff that was
there in version 1.1 is still there, and no easier or harder to use than it
was originally.

I don't think Java is slower to develop than it ever was, but if the
language or libraries don't have a feature you need to implement your
application, it can be forever to develop. You could always go to JNI, but
then you are asking for portability problems.

I completely agree.  It's almost like a children's story.  Once upon a
time....

When C++ began to fall out of favor, the C++ programming herd migrated
to Java (mainly to keep their resumes up to date and avoid
unemployment).  After arriving at Java, they discovered to their
horror that their favorite paradigms (multiple inheritance, generics/
templates, etc) were missing.

Ignoring the fact that these were the very same paradigms that had
morphed a perfectly sane and simple language, C, into the steaming
pile of complexity that is C++.   Ignoring the fact that there was a
community of non-C++ programmers already using Java who were quite
happy with it.  The herd was disgruntled.

So the herd bitched and moaned and somehow convinced Sun to ignore
hundreds of truly useful enhancements on its Bug Parade, and focus
their engineering efforts on producing Java 1.5 with Generics.

In the end, the herd won't be satisfied until they've morphed Java
into a language that is as ugly and hard to parse (by man or machine)
as their beloved C++.  At that point, Java++ or whatever it's called,
will start to fall out of favor due to its crippling complexity, high
maintenance costs, and unreadability.

Then it will be time for the herd to move on to the next up-and-coming
language.

~Glynne

I don't think so.  There is more of it, but that is canned stuff you
used to have to roll your own for.  You are better off. You can still
roll your own, or you can use a canned library maintained and debugged
and tested by others.

Genericity is hare-brained and reeks of eau de kludge. This may just
be innate to the problem, but I would hope the universe is not so
ugly.  Surely there was a simpler way.
see http://mindprod.com/jgloss/generics.html

enums greatly simplify code.

There is a little more to learn, but once you do, code is much easier
to write.

Also IDEs such as IntelliJ have kicked up development a notch.
Programming is so much less tedious than it used to be when you can
create all your getters and setters with a keyclick or refactor out a
method, or globally rename, or simply find out where something is
defined.
--
Roedy Green Canadian Mind Products
The Java Glossary
http://mindprod.com

Although Java itself has got more complicated I think most of the
frustration comes from numerous frameworks that Java developers need
to be across these days. For a web development you have got Spring,
Struts, Hibernate, JSF etc. They are all very powerful but often
overkill for smaller projects and they go out of date so rapidly.

-----
f.p.

frustratedprogrammer@gmail.com

http://frustrationsofaprogrammer.blogspot.com

C++ was rather complex from the beginning, but there
are other examples of languages becoming
much more complex over time.

The API has grown a lot. And in 1.5 they enhanced the language
itself - and are planning to do the same in 1.7.

There seems to be a philosophy that if .NET has it then Java
needs it too.

I am a bit worried, because I liked the KISS concept in Java.

Arne