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 377920
To read all comments associated with this story, please click here.
standards...
by Yamin on Mon 10th Aug 2009 16:37 UTC
Yamin
Member since:
2006-01-10

I'm an old school embedded programmer. But I've recently started doing some web development. More towards internal tools and what not.

I sit around wondering WTF have these web standards people been doing. I really do. The web gave us a new chance to develop a platform with all we learned from application development over the past 30 years... and what did we do? We repeated pretty much every mistake we made in application development for the web and some new ones to boot.

It took us sometime to learn to separate GUI presentation from application logic. Here I am looking at web code and everything is scribbled into one file. Everything is untyped...

Now don't get me wrong. I know this is how things evolve ;) I've been in more than one networking standards process to know how ugly things can get. Everyone pushing their way, trying to maintain backwards compatibility, hacking things onto current frameworks... It's certainly understandable to see how the HTML part of the web which began more as a document format ended up like this.

I don't know. These are not new problems. Event handling, manipulating objects... are all easily solved problems. It's just hacking these onto an existing base.

My own view:
The web doesn't need a new thin client. It definitely needs some better development tools and frameworks. Even if it restricts what you can do. I'd like to see a lot of the details pushed underneath. To treat a lot of the underlying stuff, the way C programmers treat machine code. Yes we know it's there. We know how it works. If push came to shove, I can deal with it. But I don't want to know the details every day at work.

Rich clients can and will become more popular. But they're not mature enough yet. I've played with Silverlight 2. You can certainly see the potential. If I had to develop any complex application (charting...) I'd most certainly use it.

Reply Score: 6