alt Hacker News>Ever since they got the delicious taste of white-labelling chromium instead of fixing ie
What exactly was wrong with Edge Legacy(not IE) based on their own engine that they need to fix, and why was Chromium a sweet taste?
AFAIk Edge Legacy was kicking ass in all benchmarks. Their only achilles heel was Google messing up Youtube and G-apps to break they way they got displayed on Edge LEgacy forcing users to switch to Chrome.
Replies
I was playing with the RTM release of Windows 10 which came with the "new Edge" browser (post-IE, pre-Chromium). It's a cool piece of software, very slick and minimal browser UI and not a hint of Copilot anywhere (since that would come ~8 years later).
I imagine it was not as compatible and it was less work to simply rebrand Chromium as Edge.
What was wrong is that they had to foot the bill. Now Google does the hard and expensive part for them.
> What exactly was wrong with Edge(not IE)
The constant fear of having Copilot shoved down your throat whenever you close and update Edge. And Microsoft homepage.
> why was Chromium a sweet taste?
Do zero of the heavy work maintaining a browser engine. Do maximum (little) work of adding AI slop.
Edge Legacy was always playing catch-up trying to be sufficiently compatible with Chrome.
And personally, I preferred the native IE UI over the Chrome-lookalike Edge UI.
I’d still have liked for Microsoft to keep maintaining their own engine, but I can understand why they didn’t.