MICROSOFT'S BIG hairy, bold plan to move his "meh" browser. The edge of Google's open source. Chrome engine was partly Google's fault.
A former Microsoft intern claims that EdgeHTML maintenance became sociable because Google continued to violate Chrome compatibility, and Edge Devs tried to add its own software.
& # 39; JoshuaJB & # 39; posted on Hacker News : "I recently worked on the Edge team and one reason we decided to quit EdgeHTML was because Google continued to make changes to the sites that broke other browsers and we could not continue . For example, they recently added a hidden empty div over YouTube videos that make the hardware acceleration fast to bail (should now be resolved in Win1
He continues to explain that without the indirect disturbance, he thought that Edge's "relatively modern" hardware shake produced better battery life results Chrome, and it was only after they had broken / fixed that Edge stopped working too.
He adds: "What makes it so sad is that their alleged dominance was not due to brilliant Chrome optimization, but because of an error in YouTube. At all, they only made the net slower."
& # 39; JoshuaJB & # 39; says he does not think that what was done on YouTube was a deliberate attempt to tune Edge's progress, but some in Microsoft think it's exactly what it was, especially when Google reversed the changes as a deterioration of Edge performance.
Microsoft confirmed last month that it moved future versions of Edge to open source engine, with EdgeHTML retained only for older Universal Windows Apps (UWP) and other compatibility usage cases.
The reaction to the news has been mixed, with some approach to the further move towards a common standard, while the second question of wisdom about having only three major web engines – Apple Safari, Mozilla Firefox and Chromium that require Chrome, Opera, Vivaldi and of course Edge.
On the plus side, it seems to have cooled down the browser war with its annoying self-serving popups, at least for the moment. μ