3 ms·
I mean, didn't they already try building their own browser engine (EdgeHTML/Chakra) and failed? I don't see Microsoft ever adopting a strategy like this. It'd
by sergiomattei 6y ago
I mean, didn't they already try building their own browser engine (EdgeHTML/Chakra) and failed?
I don't see Microsoft ever adopting a strategy like this. It'd be nice, but given the disaster that Edge turned out to be — it's highly unlikely.
- Const-me 6y agoI've used it for years before Windows Update pushed the new Chromium-based one. It worked well for me, was faster and consumed less memory than the new one. The only problem with EdgeHTML was google abusing their monopoly, read this: https://news.ycombinator.com/item?id=18697824 https://news.ycombinator.com/item?id=18697824
- garmaine 6y agoFYI you can revert to the old EdgeHTML-based browser, with a one-liner in an admin console.
- Const-me 6y agoI’ve already upgraded to 32GB RAM, migrated bookmarks, found new extensions. But thanks, will do on a laptop where I have less stuff to migrate, slower CPU with less memory, and sometimes care about power consumption. To anyone interested, here’s the manual: https://docs.microsoft.com/en-us/deployedge/microsoft-edge-sysupdate-access-old-edge https://docs.microsoft.com/en-us/deployedge/microsoft-edge-s...
- sergiomattei 6y agoYeah - I'm not arguing against its technical merits. Dumping it was mostly a business reason - it made zero sense for MS to continue making their own browser engine.