Mozilla Foundation and Opera Software Describe Joint Vision for Web Application Framework

Tuesday May 25th, 2004

The Mozilla Foundation and Opera Software have published a paper outlining their vision for Web applications. The paper, submitted in preparation for next week's W3C Workshop on Web Applications and Compound Documents, describes a device-independent Web application framework based on HTML and backwards-compatible with existing Web content. The two organisations are keen to get parts of this framework in place soon to prevent a single-vendor solution (see Microsoft's position paper) becoming dominant. Co-author Ian "Hixie" Hickson's provides more insight in a recent weblog post on the matter.

#30 Re: Re: Re: KISS *is* the right way forward...

by jilles

Thursday May 27th, 2004 11:10 AM

You are replying to this message

Best example against your argument is that I'm currently editing this message in a textarea instead of a wordprocessor. A wordprocessor would give me the convenience of spellchecking, all sorts of layout funcions cut and paste of other things than text, etc.. Those things are hard to realize using current web technologies. Doing wysiwyg text editing got a lot of oohs and ahs in the eighties yet this basic feature is still lacking in web applications while it has been perfected for nearly two decades outside the browser. We do have inline editing in browsers but compared to the real thing it is very buggy & limited.

Obviously the ease with which Avalon/Xaml can be transferred to the web is lost on you. MS has layed out the complete architecture for such applications already (and very uncharacteristically they even took security into account). It will take time to make it usuable and finish all the necessary parts and they'll probably get things not quite right in the 1.0 but my point is that we are giving them plenty of time to experiment while we still rely on obsolete, limited technology and do nothing.

A browser is far too limited for presenting content and applications. Outside a browser content and applications are much richer and much easier to manipulate. There is no technical reason for that. In the end it is not what developers are used to but what users are paying for that makes the difference. If there is one thing developers are used to (or should be used to) it is changing technology.