- Apr 10, 2011
As a developer I must say that this isn't actually true. Which is pretty much the entire problem.Nomad said:Again, your starting point in this case is the standard you mentioned. Note the relevant bolded part of my post. If your starting point is IE and the demands of IE - regardless of external standards - then everything else becomes deviant. I would also appreciate a more civil tone from you - criticize my arguments, not me personally.
The only difference between starting with IE and making your code compatible for IE later on is when you write that extra code. If you start with IE you'll be doing extra work right at the start, if you add compatibility later on then you'll be doing extra work at that time.
It's not that IE needs 60 lines of code and other browsers need 60 lines of different code. It's that IE needs 90 lines of code, including the 60 lines that other browsers need to do exactly the same thing those 90 lines are doing in IE. The other browsers aren't deviant if you start in IE, they're more efficient.
IE doesn't have it's own standard, as an alternative to the W3C standard. It's just doing different things every single version.
You can see this very simply. Open up IE, you'll have options to go into different document modes for IE7, IE8, IE9 etc. There's even another option to go into different browser modes for IE7, IE8, IE9 etc.
Now open up Chrome/Firefox/Any other browser. There's no document modes, there's no compatibility modes. There's no browser modes. That's because these browsers have standards. They're not doing different seemingly random things in each version. They have a standard which they keep to.