Praise JESUS!
Out of context: Reply #30
- Started
- Last post
- 35 Responses
- gabriel_pc0
Bruno, if I knew nothing about web scripting I would agree with you. Unfortunately I know a little bit.
Having web browsers that support malformed code are bad for a few reasons.
First, the applications themselves have to be considerably larger and more complex in order for them to read incorrect code and guess what it's supposed to mean. This results in slower page loading and poor performance overall.
Second, each time a new version of the browser comes out there's no telling whether or not the web pages that you built incorrectly will work in the new browser. Standards-compliant code is completely forward compatible.
Third, browsers that support incorrect code formatting only lead to more poorly written sites. Would you want a spell checker that instead of telling you when a word was wrong simply let it go?
Having a browser that supports incorrect code doesn't lower the barriers to web publishing, it lowers the quality and compatibility of the code.
Also, there's a whole world of accessibility reasons that make standards compliant code a must. Please read this article:
http://www.alistapart.com/storie…
and this one: