>>89
You obviously haven't witnessed the 'awesomeness' that is JSF. Or JSR 168. Or Spring. Or <insert stupidity with cool marketing name here>.
Do you enjoy marketing drivel?
Do words speak louder than actions for you?
Do you blindly take statistics pulled out of clogged toilet as truth?
Do you enjoy wasting your time for no purpose?
Do you want to be a consultant?
If you answered "yes" to all 5 questions, then Java is for you!
Want support? sure, if you take it up the ass from Sun---sorry, I mean become a 'partner' and agree not to promote any competing products no matter how much better they are...oh look, VENDOR LOCK IN, OH SHI-
>>95
Goddamn right it has always been a shit pile. If you deal with this shit on the 'enterprise' level, what ever the fuck that means, you'll see that it has gotten a lot worse. Java solutions require clustering for any kind of availability because something always broken, oh the countless times I've had to fix the shit sucking appservers in a week.
| I'd rather have three times as much clear and comprehensible code.
Pity that 3 times extra code consists entirely of pointless factories, singletons, more factories, object lookups, redirections and yet more factories. Oh, and an extra method call. That requires factories.
Do the right thing, write 100% Pure Javaless programs.
But Java isn't all bad! There's so much stupidity in the Java world that it's become a stupidity black hole, sucking stupiditity into itself make everything else less stupid; which is a GOOD thing!