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.
Permalink for comment 377941
To read all comments associated with this story, please click here.
You're forgetting one crucial thing
by Eddyspeeder on Mon 10th Aug 2009 19:05 UTC
Eddyspeeder
Member since:
2006-05-10

All nice and good, but I do not find it sensible if the HTTP protocol is not drastically changed.

First replace the wooden foundation with reinforced concrete. Then fix the plasterwork. Not the other way around.

Recent milestones are HTML5 and IPv6, but the Internet's foundation has gotten stuck with the 1997 HTTP 1.1.

Just to put things in perspective: 1997...
- the heyday of Yahoo, Homestead, XOOM and websites using frames
- the days of Flash 2.0, HTML 3.2 (4.0 was introduced in December that year) and the introduction of CSS 1.0
- the time before Napster (estb. 1999), Google (estb. 1998) and YouTube (estb. 2005)

We have been stalling an HTTP protocol overhaul for way too long. We are sending huge files using the hyper TEXT(!) protocol (which is really a hack if you look at it objectively), for which the *FILE* transfer protocol (FTP) had originally been created.

Reply Score: 2