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 377978
To read all comments associated with this story, please click here.
RE[2]: Sorry, don't agree
by snowbender on Mon 10th Aug 2009 22:49 UTC in reply to "RE: Sorry, don't agree"
snowbender
Member since:
2006-05-04

Web sites that try to act like native apps with tabs and layouts all get over complicated. Every click needs to travel roundtrip and to make it appear that it isn't you use AJAX to further complicate things.


This is simply BS. You don't need roundtrip for showing tabs and layout. And you also don't need AJAX for that. You can use AJAX to dynamically update a page. That means you load a small amount of data from the server and add that dynamically in your page. That is cheaper than web1.0 roundtrip and reloading the page.

You don't need roundtrip at all for showing tabs. You can do that with Javascript, playing with the DOM and CSS. And using a javascript library such as Dojo will give you a set of predefined components that makes it really easy to show tabs on your page, and to have buttons with rounded corners.

Don't be mistaken. I am definitely not of the opinion that every client application has to become a web application. I do think that the big power of web applications is related to deployment. Deployment or roll-out of web applications is much much easier and cheaper than for desktop client applications in for example a big company with hundreds of desktop computers.

In any case, your post shows that you are not really familiar with the technology used in web applications.

Reply Parent Score: 3