A good article by Brad Jones on the history of one of the world’s most popular browsers.
So we set about to create a new engine using IE11’s standards support as a baseline. I watched Justin Rogers, one of our engineers, press “Enter” on the commit that forked the engine—it took almost 45 minutes just to process it (just committing the changes, not building!). When it completed, there was a liberating silence when we realized what this now enabled us to do: delete code, every developer’s favorite catharsis.
In the coming months, swathes of IE legacy were deleted from the new engine. Gone were document modes. Removed was the subsystem responsible for emulating IE8 layout quirks. VBScript eliminated. Remnants like attachEvent, X-UA-Compatible, currentStyle were all purged from the new engine. The codebase looks little like Trident anymore (far more diverged already than even Blink is from WebKit).
An fascinating read. I always though that EdgeHTML would still be very similar to Trident, but apparently not.
The always interesting Friendly Bit blog has a list of techniques that don’t work in Internet Explorer 6 but do in IE7. Included in the post’s comments is a link to “When can I use…” a site that maintains browser compatibility tables for a host of upcoming web technologies.