Do we need HTML 5?
Tuesday, March 10, 2009
As far a traditional web applications go, HTML 4 has served remarkably well. We've been able to create countless database driven applications, and, once we understood how to use Ajax calls, we began to create highly interactive applications. So why is HTML 5 needed
The claim is that good application will become better
. But it all depends on your application. A typical CRUD-style application doesn't really need the cherished CANVAS HTML element. We can do without it, as typical data representation is most useful in tabular form. On the other hand, having the CANVAS element uniformly available in all browsers will make things easier for web developers, since we don't have to create convoluted logic to account for IE's lack of cooperation.
By the way, any incremental enhancement to any technology is a welcomed change. As long as all browser providers play by the rules, HTML 5 will be a great upgrade.
I'd love it if browsers conformed to the new rules the same way, but based on experience, I don't think they will - IE always tends to do things just a little differently than the standards. It's taken a long time for web developers to understand that just because it works in Internet Exploder doesn't mean that it was done right - and some of them still don't get it.
I'd prepare for another round of "this page must be viewed in IE" websites once HTML 5 is out and lazy web developers start using it.
Of course, nothing would make me happier than being wrong about this...
Joe, I don't think we'll stop hearing about compatibility issues, unless all browsers use an open sourced HTML rendering engine. At this point, however, there is no need for multiple browser.