Microsoft is building a Chromium browser to replace Edge on Windows 10
121–130 of 774 posts
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#122Earlier quoted context omitted.
It just depends on how far you're trying to push these browsers. Chrome has a lot of crazy cutting edge APIs which allow amazing developer and therefore user experiences. For example, IntersectionObserver, which allows developers to know when a part of a page is active, and respond accordingly; Safari doesn't even implement IntersectionObserver, even though it's been a standardized spec since like 2013. It might seem…
Oh sure, I know. Often wondering if I should even try with Safari. I was trying to ask how Edge was broken.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#123Sad news. Chrome is an energy hog on the Mac compared to safari. It probably won’t be as tied to the OS APIs as Edge was.
> Chrome is an energy hog on the Mac compared to safari. It seems that with more interest in that, it's likely to improve. > It probably won’t be as tied to the OS APIs as Edge was What makes you say that? Seems like they could integrate it more or less exactly the same way.
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#124Interesting 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?…
dHTML FTW!
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#125Earlier quoted context omitted.
> The Chromium engine itself is open source Being open source is a red herring in this instance. Say that Chrome implements a web feature you don't like. You fork the browser and remove that feature. But websites expect Chrome, and they use that feature, so your fork doesn't work with those websites. Say that Chrome refuses to add a feature you want. You fork the browser and add the feature. But websites expect Chrom…
Your examples have nothing to do with whether you use Chrominum engine, though. Say that Chrome implements a web feature you don't like. MS use their own MSengine for their Edge browser that doesn't have that feature. But websites expect Chrome, and they use that feature, so MS Edge doesn't work with those websites. Say that Chrome refuses to add a feature you want. MS use their own MSengine for their Edge browser th…
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#126A number of the comments mention monoculture. But where does monculture end and a solid reliable and honest standard begin? For exampke, at some point the power grid and gasoline formulations were standardized, yes? TV screen sizes, tin cans and shipping containers. Is the browser not the shipping container of our time? To call W3C a standard and then have different implementations is no standard at all. That is the…
Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#127Re: Microsoft is building a Chromium browser to replace Edge on Windows 10
#128As 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.
WTF do you mean "lead to sites not bothering to be made compatible with Firefox"?? If Firefox follows the published HTML standards then there wouldn't need to be any special compatibility effort made by us web devs! That is exactly what made I.E. (and Edge) so cr@ppy in the first place!! /facepalm