Why IE v.next? Why not IE2 v1
Chris Wilson on the IE team blogs about the current thread on the HTML WG where he fights his corner for maintaining backwards compatibility in IE against becoming more standards compliant. It’s a good post too. But here’s a thought - why not leave IE as it is and release a new completely compliant (as far as possible) browser which is not called Internet Explorer? The Expression team already wrote a new renderer from scratch that now sits in Expression Web and VS Orcas, so why not build around that and not worry about backward compatibility. If it’s not the same product (and you can make it stand alone too so it can be uninstalled if required ;) you don’t need to worry about it.
So, we’re having a fun thread [http://lists.w3.org/Archives/Public/public-html/2007Apr/0612.html] on the HTML WG. I’m explaining what Microsoft must do, given the half-billion or so users that rely on us to not break their web experience. A certain contingent disagrees with me (okay) and seems to want to beat it out of me (not okay).
Source: The joy of being me [http://blogs.msdn.com/cwilso/archive/2007/04/14/the-joy-of-being-me.aspx]Posted on April 16, 2007 #Geek Stuff