Earlier quoted context omitted.
Mmmm isn't this effectively Gecko/Blink/WebKit now?
Blink and WebKit cannot be considered as separate implementations - their codebase is in sync AFAIK.
Microsoft is building a Chromium browser to replace Edge on Windows 10
51–60 of 774 posts
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#52Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#53Interesting, but what I really, really want them to do is EOL IE 11 so that the web can move forward without feeling guilty about the X% of users still on it. IE 11 has unfortunately become the new IE 6. As it is right now I believe the IE 11 EOL is tied to the Windows 10 EOL...which is not happening anytime soon. Many frameworks are dropping support for it anyway so I guess it will end up being defacto desupported.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#54That's just the disaster. And the end of W3C standard development process. AFAIR it should be 3 independent implementations of the feature in order for Draft to reach Recommendation status. So technically all that means that web standards will be written by WebKit team alone. Sic transit Gloria mundi, sigh.
Fair concern. On the other hand nobody uses Edge on Windows 10, do they? In my limited experience users seem to still use IE or go to Chrome or Firefox.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#55Earlier quoted context omitted.
Fair concern. On the other hand nobody uses Edge on Windows 10, do they? In my limited experience users seem to still use IE or go to Chrome or Firefox.
I use it as much as possible. Its user experience on touch windows devices (Surface Go in this case) is several orders of magnitude better than Chrome and Firefox... is not a usable browser, performance-wise in my experience. Edge is brand new, and foolishly branded to look like IE, this might stop average users who know about getting Chrome from using it. But it shouldn't. It's extremely rare that I'm forced to swap…
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#56To call W3C a standard and then have different implementations is no standard at all. That is the nature of guidelines. The fact that said "standard" so often led to a suboptional UX only poured salt on the wound.
Maybe this really is bad news? But there doea seem to be some upside, monoculture or not.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#57https://twitter.com/SwiftOnSecurity/status/10697763353362923...
“This isn’t about Chrome. This is about ElectronJS. Microsoft thinks EdgeHTML cannot get to drop-in feature-parity with Chromium to replace it in Electron apps, whose duplication is becoming a significant performance drain. They want to single-instance Electron with their own fork”
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#58If Microsoft really does this and makes the Chromium based browser the default in Windows, what is the value proposition of installing Chrome? Presumably all the websites will work exactly as they do in Chrome and it will be no faster or slower?
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#59Broken shit should die. And Edge was definitely broke. Safari is next, with 5% market. Chrome is the clear winner in the end.
If Edge is broken, I can't really tell beyond what I think were some quirks still present when I was trying to target it last year. It wasn't that bad, but it didn't seem like Microsoft was making as big an effort towards it as they could have.
What disappoints me is that, for reasons unknown, Microsoft didn't choose Gecko as its rendering engine, as it(and Firefox) could benefit from the extra attention and money from Microsoft.
EDIT: I initially said "Spidermonkey" when I meant to say Gecko.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#60Earlier quoted context omitted.
Mmmm isn't this effectively Gecko/Blink/WebKit now?
Blink and WebKit cannot be considered as separate implementations - their codebase is in sync AFAIK.