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.
Thread beginning with comment 377906
To read all comments associated with this story, please click here.
by hapalibashi on Mon 10th Aug 2009 14:23 UTC
Member since:

The web works because of the way it has evolved. You can't just take that success and transplant it onto another stack.

"Graphic designers would use GUI tools exclusively to work with this binary format, which works out perfectly as nobody wants to muck around with a markup language like HTML anyway."

*nobody* ?? Really? What evidence supports this?

Would they prefer to rely on expensive paid-for or free "design" tools.

Either sounds like a *major* step backwards, vendor lock-in, risky.

No. The existing stack is open, flexible, proven and get this: *not difficult*.

If anything, some effort needs to go into improving JS frameworks, specifically AJAX frameworks (mootools, prototype, JQuery etc), building on HTML5. Google and Apple will most likely make a major contributions here.

Other improvements could include efficient media handling, lower down in the stack (including TCP - which is something Google *is* looking at), not in the parts that are proven to work.

Reply Score: 4

RE: Huh?
by google_ninja on Mon 10th Aug 2009 18:40 in reply to "Huh?"
google_ninja Member since:

Completely agree. The big problem with the web is that the W3C blows. We need a process that doesn't take 5-10 years to come up with a standards recommendation.

Semantic elements, web workers, canvas, border-radius, gradient, and column-layout solve most of the things that are irritations with writing for the web right now. Unfortunately, it is going to take another five years or so before this spec gets out the door, and people can start working on the next list of annoyances.

Reply Parent Score: 4

RE[2]: Huh?
by kragil on Mon 10th Aug 2009 19:13 in reply to "RE: Huh?"
kragil Member since:


I think every platform that evolves and adapts will be very hard to beat/replace. And it seems open standards and platforms are inherently better at this than some grand brainchild of some company/single developer.

But there are some use cases where HTML/JS won't work well that is why Google is working on native client.

Reply Parent Score: 2