Live data from Hacker News

Chromium-based Edge preview builds

blogs.windows.com

81–90 of 111 posts

Re: Chromium-based Edge preview builds

#81
post #28

I wish they've would have gone with Firefox's Quantum, in order to try and at least balance out web market shares. MSFT no longer has any leverage in the web, so trying to keep it fair and accessible (no browser monopolies) should be a priority for them (especially since they have quite a few web platforms like office 365)

[deleted]

Re: Chromium-based Edge preview builds

#82
post #79
post #49

Earlier quoted context omitted.

I hope Apple would turn away from webkit and invested into firefox. They're both privacy focused so it seems like a logical choice.

Stupid question probably... since I haven't had an iPhone for a couple years. Is Safari there still a thing? On my Mac I'm not using Safari at all. Havent opened it a single time since i got my latest MacBook - well I must have to download firefox but I dont remember. I remember at one point Apple wouldnt allow any other browsers rendering engines on iOS - is that still the case?

Safari is still a thing and still under active development.

All iOS browsers use Safari WebKit under the hood.

Re: Chromium-based Edge preview builds

#83
post #79
post #49

Earlier quoted context omitted.

I hope Apple would turn away from webkit and invested into firefox. They're both privacy focused so it seems like a logical choice.

Stupid question probably... since I haven't had an iPhone for a couple years. Is Safari there still a thing? On my Mac I'm not using Safari at all. Havent opened it a single time since i got my latest MacBook - well I must have to download firefox but I dont remember. I remember at one point Apple wouldnt allow any other browsers rendering engines on iOS - is that still the case?

iOS apps can use whatever rendering engine they want. The restriction is on JIT -- Apple doesn't allow apps to compile native code on the fly, which modern JavaScript engines like V8 do. The exception is Apple's own JavaScriptCore, which works with WebKit.

In theory you could have Firefox Quantum as a tenderer with JavaScriptCore as the JS engine, but that might be more work than it's worth.

Re: Chromium-based Edge preview builds

#84
post #66

Earlier quoted context omitted.

Why would they do that when they essentially control an entire browser engine?

Because their browser engine sucks, people just use it on mobile (iOS) because they basically have to in order to open any link. Every full time job I've had I've been issued a MacBook and step 1 of setup was "install Firefox or Chrome". Safari is one of the few things that truly outright blows about the Apple ecosystem.

Safari is a fantastic browser, actually.

It's as fast as Chrome and Firefox. (Firefox is curiously sluggish on the Mac, even when the latest Quantum improvements.)

Sure, it tends to lag behind when it comes to adopting certain newfangled web technologies, but it supports everything that's important (even web workers now? I think?), and it's super stable.

I use Chrome for web development, though, because of the built-in dev tools. (The tools are pretty gnarly for 2019, but they get the job done, for the most part.)

Re: Chromium-based Edge preview builds

#85
post #20

Earlier quoted context omitted.

They're using V8. https://github.com/Microsoft/ChakraCore/issues/5865#issue-38...

Which begs the question why would anyone use Edge when they can use Chrome?

Not sure that's the question when you already have edge... I think it turns into...

question is, why use chrome when edge is basically chrome but already installed on windows out of the box?

Re: Chromium-based Edge preview builds

#86
post #49
post #28

I wish they've would have gone with Firefox's Quantum, in order to try and at least balance out web market shares. MSFT no longer has any leverage in the web, so trying to keep it fair and accessible (no browser monopolies) should be a priority for them (especially since they have quite a few web platforms like office 365)

I hope Apple would turn away from webkit and invested into firefox. They're both privacy focused so it seems like a logical choice.

Sadly Apple took the wind out of my all-time favorite browser, Camino, née Chimera, when they started up the WebKit/Safari project by hiring away key people like Dave Hyatt: https://donmelton.com/2013/01/10/safari-is-released-to-the-w...

Re: Chromium-based Edge preview builds

#87

Earlier quoted context omitted.

I agree with this sentiment. Edge was an extremely fast browser and I think it lost before it was even released simply by using similar branding to Explorer.

Edge lost because, even in April 2019, it is a buggy pile of shit that lacks fundamental features it's competitors have and chokes on web pages constantly. (I'm forced to use it for work.)

In truth I didn't use edge much myself, but for the slim number of uses the speed was nice.

Re: Chromium-based Edge preview builds

#88
post #20

Earlier quoted context omitted.

Which begs the question why would anyone use Edge when they can use Chrome?

I _believe_ they are doing this because they are heavily investing in Electron (Skype, Visual Studio Code, Teams, more). Having both Chromium and V8 be part of Edge (and the OS) means they can remove them as bundled dependencies from Electron on Windows and lighten the payload of those apps. I wouldn't be surprised if we see future Windows builds of Electron becoming smaller because of this. There is not proof of thi…

Porting VS Code to Chrome OS, without need for an electron-based GTK app inside a 'Linux container'?

https://github.com/Microsoft/vscode/issues/1031

Re: Chromium-based Edge preview builds

#90
post #77

Earlier quoted context omitted.

Why would they do that when they essentially control an entire browser engine?

Because safari will sooner or later become another Edge. Apple doesn't invest enough into safari and now it's a browser which is most behind in terms of technologies.

Apple's Safari investment is focused on features like tracking prevention and anti-fingerprinting. Stuff for users at the expense of developers.
Post reply on HN