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 377976
To view parent comment, click here.
To read all comments associated with this story, please click here.
Delgarde
Member since:
2008-08-19

HTTP *works*. Otherwise the Internet would not have become what it is today. But I'm not for the "if it ain't broken, don't fix it" mentality. HTTP was not meant to do what it does today.


In what way? As you say, HTTP works. In what way is it deficient, that you see the need for a replacement? Why would anyone use your replacement, if HTTP works?

Reply Parent Score: 2