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 377923
To read all comments associated with this story, please click here.
I don't think the web needs to be rewritten
by sto1c on Mon 10th Aug 2009 17:16 UTC
Member since:

If we're planning forward we should remember that to date technology has kept far ahead of demand. Ie broadband capacity will increase so fast that saving '5%' of traffic will make very little difference to the interneet. Besides, a lot of the text sent (HTML) can be gzipped behind the scenes today, making it only slightly larger than a purpose made binary format.

Whilst a session based network model sounds attractive, so much work has gone into making the current system work with sessions that it would be a hard sell asking developers to move to any new system. They would want to know what new things the system can do. Since sessions can already be abstracted with things like Rails and Javascript libraries the web developer doesn't need to worry about the implementation details at the moment.

I don't understand the criticism of the current technology as insecure. Developers will always be able to write insecure software. The current TLS (https) system allows complete security for the end user.

I do agree that Flash should go away for the benefit of everyone. The best way to achieve this being to integrate more functionality into the current systems (like the HTML 5 video tag, and SVG).

I consider it far more likely that the only thing now capable of replacing the the web standards that exist, are later versions of those same web standards. If you want to make the web different, I think you'll have to join the standards bodies, rather than replace them.

If you haven't seen it already, I strongly recommend watching the demo of Google's Wave at to really see what is possible with the current technology. They talk specifically about how the minutia of the low-level implementation is taken away from them by the Javascript libraries they used to create Wave.
There's too much room for the current technology to grow for it to be replaced at this point.

Reply Score: 3