Linked by mufasa on Mon 10th Aug 2009 12:25 UTC
Web 2.0 The web browser has been the dominant thin client, now rich client, for almost two decades, but can it compete with a new thin client that makes better technical choices and avoids the glacial standards process? I don't think so, as the current web technology stack of HTML/Javascript/Flash has accumulated so many bad decisions over the years that it's ripe for a clean sheet redesign to wipe it out.
Thread beginning with comment 377952
To read all comments associated with this story, please click here.
Java Will Save The World!
by zlynx on Mon 10th Aug 2009 20:11 UTC
Member since:

This article sounds an awful lot like some old Sun Java stuff from long ago.

All we need to do is make everything run Java! Then we run Java to compute on the server, Java to display on the client, anyone can run everywhere and everyone can have a pony!

Honestly, this Java dream is a lot more realizable today than it was in 1999, but no one seems to be doing it.

Reply Score: 6

RE: Java Will Save The World!
by dmarsh on Mon 10th Aug 2009 21:56 in reply to "Java Will Save The World!"
dmarsh Member since:

Very true. I came to the same conclusion when thinking about the issues the author expressed.

Reply Parent Score: 1

RE: Java Will Save The World!
by Eddyspeeder on Mon 10th Aug 2009 21:56 in reply to "Java Will Save The World!"
Eddyspeeder Member since:

And I think the reason why this is, can be found in an interesting discussion a few weeks back on OS News. You had your "C++ OOP" camp, your "(O-)C" camp and your "Java" camp.

I think this diversity in approaches is good; it will allow every developer to choose his own approach, which is likely to yield far better outcomes than any unified construction would (especially if that were to be a compromise between the precompiled / semicompiled / scripting camps).

Reply Parent Score: 1