I suspect now that FF has so much market share, those same webmasters have to do the same tweaking and complaining to get the page to display right with Gecko-based browsers. That's terribly inefficient. If browsers were actually standards-compliant, all it would take was running the html and css through w3 validators, then admiring it in any browser and knowing it will look the same regardless of the browser engine. That's the beauty of standards. Efficiency.
I wish that were possible. As a fledgling web developer I am presented with an option: do I design sites that are standards compliant, or do I tweak my stylesheet so that IE and Gecko will display them nicely? Unfortunately I have to choose the latter, because otherwise my clients will whine about everything being messed up in IE (and probably Firefox also).
It's ridiculous that they defend IE by claiming "no pages seem horribly messed up." Clearly the author is not a web developer. If he were, he would know that the reason the pages display correctly in IE is javascript hacks, css workarounds, web developer headaches, Dean's IE7 javascript library, a separate stylesheet for IE, etc...
It's not that IE is inherently displaying the sites correctly, it's that the site developers were forced to make them play nice with IE.
Slashdot Mirror
I suspect now that FF has so much market share, those same webmasters have to do the same tweaking and complaining to get the page to display right with Gecko-based browsers. That's terribly inefficient. If browsers were actually standards-compliant, all it would take was running the html and css through w3 validators, then admiring it in any browser and knowing it will look the same regardless of the browser engine. That's the beauty of standards. Efficiency.
I wish that were possible. As a fledgling web developer I am presented with an option: do I design sites that are standards compliant, or do I tweak my stylesheet so that IE and Gecko will display them nicely? Unfortunately I have to choose the latter, because otherwise my clients will whine about everything being messed up in IE (and probably Firefox also).
So you're arguing that the ends justify the means...?
It's ridiculous that they defend IE by claiming "no pages seem horribly messed up." Clearly the author is not a web developer. If he were, he would know that the reason the pages display correctly in IE is javascript hacks, css workarounds, web developer headaches, Dean's IE7 javascript library, a separate stylesheet for IE, etc... It's not that IE is inherently displaying the sites correctly, it's that the site developers were forced to make them play nice with IE.