Imx Fix in my experience
« prev next »

March 14, 2002 9:31 AM

I couldn't resist to post my response to a message on the WebDesign list...

at 3/14/02 8:28 AM by Zak McGregor wrote:



> "We've been looking at how people work on the Internet, how people use

> Internet applications, and what we saw was that...HTML was breaking down

> in a lot of cases," said Eric Wittman, Macromedia's director of product

> management for Flash. "


> So I gather that Macromedia is gunning to replace an open standard with

> a proprietary technology, and wants to rid the world of HTML? This seems

> absurd, but it's not April 1st yet. 

Be sure to keep within context here. This is in reference to *web applications*, not normal, content based, web sites.

I have worked on a few complex web applications, and HTML was indeed breaking down on us. The reason being that Netscape 4.7 is a completely different browser to code for than IE (which we all know) and both have odd bugs that cause application crashes. Quite often, HTML and some incredibly sophisticated JavaScript was just barely able to meet the business needs of the client.

If we could eliminate the (business and development) liability of wildly inconsistent DOM, HTML and JavaScript implementations, we would have a massively easier (and cheaper!) way to built a web app that could be called robust. Also, not having anything resembling a client side IDE is a problem for serious web app development. Using the Flash authoring kit (or LiveMotion) can mitigate that problem to some degree.

> What does this mean for the vision of client-independent content

> delivery? How has Macromedia addressed it's inherent weaknesses when

> compared to html, for example word weighting, full indexability [sic], the

> ability to display on devices other than windowed GUIs, the inability to

> link to specific information in Flash, bookmarking issues, printing

> issues, etc?

When it comes to the web applications I have worked on, issues like "full indexability" do not matter. What does matter is predictable results in a highly complex environment. In me experience, DHTML can't provide that.

I welcome any technical advances in Flash technology to make web apps more robust, usable, and "codeable." I don't feel like that will be any threat to (X)HTML's future.