3 ms·
I was referring more to their failure with Edge 1.0, where they did mostly jetison the legacy cruft and start a greenfield project to match Chrome and Safari. T
by thrower123 5y ago
I was referring more to their failure with Edge 1.0, where they did mostly jetison the legacy cruft and start a greenfield project to match Chrome and Safari. They threw a lot of effort into a mediocre product that almost no one used.
- cweagans 5y agotbh, I forgot about that, but it wasn't exactly a green field project, right? They started with a fork of Trident. It'd be hard to know without an engineer from Microsoft chiming in, but it's entirely possible that the first bit of EdgeHTML was just Trident with all of the compatibility modes turned off. Maybe they removed them entirely, but just removing those piles of code doesn't fundamentally change the thing they hooked into, right? All the plumbing to support old cruft could still be there, which would make working on EdgeHTML almost as hard as working on Trident. Mozilla incubated Servo with a team of five (as of ~2014). It's not a complete browser on its own by any means, but surely that points at some degree of possibility.