Live data from Hacker News

Microsoft's new browser and the Windows 10 January preview build

blogs.msdn.com

1–10 of 29 posts

Re: Microsoft's new browser and the Windows 10 January preview build

#2
It's interesting that they decided to start from scratch with a new rendering engine. (I imagine the UI itself could have been updated without a lot of trouble.)

They probably looked at the thousands of special cases in the old spaghetti code, maybe took a gander at the Blink/Webkit sources ;-), and then decided, "Hang it, we can do this ourselves, and do it right." Likely a pretty fun project, betting against the "never start from scratch" common wisdom of the crowd.

Re: Microsoft's new browser and the Windows 10 January preview build

#4
post #2

It's interesting that they decided to start from scratch with a new rendering engine. (I imagine the UI itself could have been updated without a lot of trouble.) They probably looked at the thousands of special cases in the old spaghetti code, maybe took a gander at the Blink/Webkit sources ;-), and then decided, "Hang it, we can do this ourselves, and do it right." Likely a pretty fun project, betting against the "n…

Curious that they're calling it a 'new' rendering engine at all. I could have sworn they said somewhere that it was still the same Trident engine, but without the legacy IE bits. Also, according to Paul Thurrott [1], the browser team was considering WebKit/Blink and ultimately decided to stick with Trident – apparently because of Google's control over Blink.

[1]: https://www.thurrott.com/windows/windows-10/470/maybe-window...

Re: Microsoft's new browser and the Windows 10 January preview build

#5
post #2

It's interesting that they decided to start from scratch with a new rendering engine. (I imagine the UI itself could have been updated without a lot of trouble.) They probably looked at the thousands of special cases in the old spaghetti code, maybe took a gander at the Blink/Webkit sources ;-), and then decided, "Hang it, we can do this ourselves, and do it right." Likely a pretty fun project, betting against the "n…

Curious that they're calling it a 'new' rendering engine at all. I could have sworn they said somewhere that it was still the same Trident engine, but without the legacy IE bits. Also, according to Paul Thurrott [1], the browser team was considering WebKit/Blink and ultimately decided to stick with Trident – apparently because of Google's control over Blink. [1]: https://www.thurrott.com/windows/windows-10/470/maybe-…

Thanks, that's a helpful link.

'Twould be delightful to know just how they treated the existing Trident sources...

Post reply on HN