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 377914
To read all comments associated with this story, please click here.
RE: Sorry, don't agree
by FunkyELF on Mon 10th Aug 2009 15:32 UTC in reply to "Sorry, don't agree"
FunkyELF
Member since:
2006-07-26

Given the choice between client side or web development, I will choose web every time, not for any other reason then I enjoy working with the technology.


I will choose client every time. Creating a client side app that dynamically creates tabs is easy. Creating rounded buttons is easy.

On the web, you can dynamically create tabs on the server side with PHP / Python / CGI / whatever. But then you need to use CSS somehow to have the currently selected tab appear highlighted. If each entry in your menu has its own CSS class you now need to dynamically generate CSS. What a pain. Alternatively you could use Javascript to make it appear highlighted. Now you're using three different technologies all loosley bound together.

Now, go and create a nice rounded button. You need all sorts of CSS hacks to do that. You need 5 different image files. Go change the color of it and you need to split it up again.

Don't get me started on layouts.

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.

If you dissect a native app you may find complications as well. You could say every click needs to travel round trip through layers of APIs down to the kernel and system interrupts back up to the userspace program. The thing is though, that this is transparent to the user as well as the developer. Maybe the web just needs better tools to make development nicer. GWT looked pretty good from the beginning and is looking even better with the changes that Google Wave needed. Maybe GWT or other technologies like it are the answer. Haven't read about SproutCore since it came out...not sure if it is similar to GWT or not.

Reply Parent Score: 5