41–50 of 774 posts
That'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.
Chromium has greater share, so I think it would be more the Chromium team.
Earlier quoted context omitted.
Why are you citing Safari's 14% market share when the person to whom you responded was stating that if it's true that Edge will become Chromium-based, then browsers running on Chromium will represent something like 66% of the world's web engine share. Heck, it's already 59%, over half. With Opera, Vivaldi, and Edge (or whatever Anaheim will become), we're talking two thirds of all browsers being based on one engine.…
I'm saying that WebKit can't be a monoculture because Safari only has 14% market share. It doesn't matter if other devices and browsers that no one actually uses are WebKit.
And while iOS has the greatest market share for mobile, you're right, WebKit doesn't have the greatest market share for general browsers. That's definitely Chromium, now on Windows, macOS, Linux, iOS, Android, your mum's toaster, just about every 'native' web app…
Side note: I guess we should really be saying Blink, that's the name of the engine. But even if, say, you use Google Chrome on iOS, backed by WebKit, that usually makes you a Google Chrome, backed by Blink, user on the desktop.
That'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.
That'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.
Mmmm isn't this effectively Gecko/Blink/WebKit now?
If 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?
I try to avoid Google as much as possible these days, thus it's funny because I never thought I'd consider using a Microsoft browser instead of a Google one. I think this is a potentially good move on Microsoft's part(the EdgeHTML thing turned out not to be).
Broken shit should die. And Edge was definitely broke. Safari is next, with 5% market. Chrome is the clear winner in the end.
Broken shit should die. And Edge was definitely broke. Safari is next, with 5% market. Chrome is the clear winner in the end.
Honestly asking...