171–180 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.
Mmmm isn't this effectively Gecko/Blink/WebKit now?
Earlier quoted context omitted.
How is the situation better if there are two browsers with 50% market share? You still can’t add a new feature the other side doesn’t want, because 50% of users won’t be able to use it. Any feature that requires a site owner to do something to support it isn’t going to be added.
You've just illustrated the advantage of a polyculture: changes to the platform are not unilateral decisions, and therefore require discussion, communication, and documentation. Furthermore, if one actor tries to do something out of blatant self-interest that would be a detriment to the platform as a whole, that action can be blocked. With a Google monoculture, at the end of the day, the web will be whatever the CEO…
So long as the players are well behaved, having a single dominant browser is beneficial. How much time, energy, productivity, and money has been lost on cross-browser (in)compatibility wrangling?
Interesting theory and thread: https://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”
The irony. They had HTA apps (running on IE engine which still work more or less, I replaced most default Win10 apps like the image viewer and the "groove" music player with a version of them built with HTA since they were slow as hell to start up) for 20 years already, they did barely anything with it, they didn't really invest seriously in a good browser engine (Edge isn't) and now all they can do is use Google's?…
As a firefox fax, I hope this isn't true. The dominance of chrome isn't good for anyone. This will lead to (even more) sites not bothering to be made compatible with Firefox. We are headed back to the "designed for IE" days.
My understanding is that they'll be using the Chromium engine underneath, but still their own Edge "browser" and UI on top. IMHO, I personally think it's a good thing to consolidate on one engine to render HTML cross-platform for these two reasons: 1. Web developers no longer need to worry about supporting CSS and other edge-cases across various browser engines. 2. The Chromium engine itself is open source. There are…
Earlier quoted context omitted.
Honestly having trouble making a coherent strategy out of those words, despite knowing what all of them mean. Seems like at the least it is written with way more confidence than could possibly be appropriate.
"drop-in feature-parity with Chromium" == They want to be able to replace Chromium with their own engine, but it must be very compatible. "duplication is becoming a significant performance drain" == Every electorn app bundles its own browser engine (as opposed to a single browser engine for the whole OS, like a shared library), which increases system RAM usage and hinders performance. "They want to single-instance El…
I can see that it increases disk space, but everything on top of that is questionable. I believe DLLs will share/reuse memory pages even if they were downloaded in separate bundles.
As a firefox fax, I hope this isn't true. The dominance of chrome isn't good for anyone. This will lead to (even more) sites not bothering to be made compatible with Firefox. We are headed back to the "designed for IE" days.
My understanding is that they'll be using the Chromium engine underneath, but still their own Edge "browser" and UI on top. IMHO, I personally think it's a good thing to consolidate on one engine to render HTML cross-platform for these two reasons: 1. Web developers no longer need to worry about supporting CSS and other edge-cases across various browser engines. 2. The Chromium engine itself is open source. There are…
Mozilla is Poland and is destined to get f*cked as their market share drops and any negotiating leverage they have to get Google TAC money disappears (they're more like Saudi Arabia is to the US, a vassal state, rather than a Great Power).
These are dire times for the web. Only Vestager can save us now.
As a firefox fax, I hope this isn't true. The dominance of chrome isn't good for anyone. This will lead to (even more) sites not bothering to be made compatible with Firefox. We are headed back to the "designed for IE" days.
(Obviously, MS will maintain their own fork and can permanently fork away whenever they want/need to, I guess, so it's not like they've locked themselves in forever, but still)
I actually wasn't aware of the problems with Edge. This is the first I've heard of them... I hadn't heard much about it from either devs or users, so I assumed lots of people were more or less happily (or at least uneventfully) using it as Windows' default browser.
Never thought I'd be sad to see Internet Explorer (or its descendant) bite the dust, given what a plague upon humanity IE was for so many years, but I'm not sure this is the happy ending we might've wished for.
Earlier 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…