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.
Okay, if we ignore the obvious hypocrisy, Molyneux has some really good points.
Molyneux commented, “The bizarre thing is a huge amount of effort and time and money goes into researching the tech, like the Kinect tech and scanning the bodies, and there’s always this one line that hardware manufacturers – whether it be Microsoft or anyone else – say and that’s ‘we can’t wait to see what happens when it gets into the hands of developers.’ Now if Apple had said that when they introduced the iPhone, I don’t think we’d ever end up with the iPhone! What really should happen is that they put a similar amount of money into researching just awesome real world applications that you’ll really use and that work robustly and smoothly and delightfully.”
Microsoft’s E3 media briefing—the first of the press conferences—just ended. Giant Bomb has a recap of the salient points.
A great paper on Agile adoption in a large corporation. The complete article can be found here (PDF).
The registration site is up.