Follow Slashdot blog updates by subscribing to our blog RSS feed

 



Forgot your password?
typodupeerror
Java

Java's Greatest Missed Opportunity? 362

jg21 writes "It looks like Bruce Eckel has hit the nail on the head again. No sooner did he finish stirring debate by writing about the 'departure of the Java hyper-enthusiasts,' previously discussed here on Slashdot, than he now rubs salt in the wound by highlighting in AJAXWorld Magazine how and why Java missed its golden opportunity to become the language undergirding Rich Internet Applications. He comments: 'We must ask why Java applets haven't become ubiquitous on the internet as the client-side standard for RIAs....This is an especially poignant question because Gosling and team justified rushing Java out the door (thus casting in stone many poorly-considered decisions) so that it could enable the internet revolution. That's why the AWT and Applets were thrown in at the last second, reportedly taking a month from conception to completion.'"

Comment Re:How do people have time for this? (Score 2, Insightful) 397

I have a full time job (game developer) and I'm part of one of the high end WoW guilds here in the US, http://www.elitistjerks.com/

We raid four or five nights a week. It's scheduled during the evenings and we try to keep our raids to a maximum of four hours. I get home from work, eat dinner, then raid in the evening. I'd rather be doing that then watching mindless television or something. I'd say I play around 12 to 20 hours of WoW a week and quite enjoy it. Sure, that's more than a casual player who plays it a couple hours a week, but I'm not putting 80 to 100 hours a week into the game.

Comment Re:However (Score 5, Insightful) 330

Actually the old code might be better. And I don't defend blindly.

It has been my repeated experience that "Cruddy and complex" code is that way because the problem space is cruddy and complex and thats what bugfixes do to code.

You throw out that complexity and you throw out accumulated knowledge. I have yet to see a second system or third or fourth that managed to keep the bugfixes of the previous system. These issues return and they are accompanied by new ones.

In this case there might be a reason to thow out this particular baby with this particular bathwater: the only thing that new code gives you is resident experts on the new code. If you have staff turnover (Which MS always does), they may have already lost the resident experts on the previous design.

So that brings up the next point: MS may now be jumping its proverbial code shark: They've not increased in price in 3 years: stock options are worthless, they're losing people, and the hardware vendors are saying "When are you going to get us a decent 64 bit system?". They can't seem to ship secure code and now they throw out working subsystems, possibly because they've got a brain drain. MS owns the office market, but they're starting to really fall behind in shipping modern security at the OS level.

Slashdot Top Deals

Know Thy User.

Working...