Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Chromium-based Edge preview builds

blogs.windows.com

Post reply on HN
Print view View original

101–110 of 111 posts

Re: Chromium-based Edge preview builds

#101

Post by qalmakka »

metildaa wrote: post #94
spinningslate wrote: post #47

Earlier quoted context omitted.

Agreed. Browser diversity might be a pain for developers, but concentrating 2 of the 4 dominant end-user computing platforms on the same browser engine doesn't sound like a positive step for users [0]. Particularly when the engine in question is developed and maintained by one of two primary surveillance tech firms on the planet. Perhaps I'm too jaded, but there's an unmistakable smell of the fishy about this. Domina…

Apple will likely stick to Safari based on their Webkit fork. Look at their stewardship of coreutils and the graphics stack on MacOS, its plain to see that they just don't care if MacOS is 5+ years behind the curve on features and performance if its not hurting battety life for most users. Gaming on MacOS has become a much more limited experience than on Linux (blame Valve for this) or Windows. Apple wields a big sti…

I think the blame for the insignificance of macOS as a gaming platform chiefly lies on Apple's shoulders and their staunch refusal in creating adequately powered desktops at reasonable price points. As long as the majority of Macs are laptops with Intel iGPUs porting anything more graphically complex than Dota 2 is pointless. I think there are more people with custom <$900 builds with decent mid-tier AMD or NVIDIA GPUs than people with extremely expensive Macs with Vega or RX580 cards.

Re: Chromium-based Edge preview builds

#102

Post by qalmakka »

atombender wrote: post #97
est31 wrote: post #92

Earlier quoted context omitted.

> iOS apps can use whatever rendering engine they want. The restriction is on JIT Wrong. > 4.7 HTML5 Games, Bots, etc. > your app must use WebKit and JavaScript Core to run third party software and should not attempt to extend or expose native platform APIs to third party software https://developer.apple.com/app-store/review/guidelines/

You're not contradicting me. The section you're quoting is not about this, by the way. You want section 2.5.2: "Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps."

Yeah, but if you read carefully, section 4.7 explicitly says that you must use WebKit and JSC to run third party software. Therefore, you can use your own engine to render your app (see games or Google's Flutter), but you cannot use it to render third-party content (thus making impossible to create a browser)

Re: Chromium-based Edge preview builds

#103

Post by vegasdew »

codycraven wrote: post #91
millstone wrote: post #90

Earlier quoted context omitted.

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

I've seen what happens to web browsers that trail behind the industry in features. It doesn't matter how nice the privacy features are, when a user encounters web site after web site that doesn't work right in their browser, they eventually each out to a more technical friend that recommends trying browser X. When browser X fixes their problems, they never return.

iPad / iPhone are captive rich markets, where only Safari is available. So companies/devs will keep on testing/supporting for it.

Re: Chromium-based Edge preview builds

#105

Post by cmroanirgo »

fgonzag wrote: 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 was actually gunning for them to continue with edge, and hoping that they'd finally make it cross platform. That they are trying out a drop in compatible nodejs using their js (chakra) was really appealing too. [0]

Ironically, it was one of the few technologies coming from ms that I was interested in.

[0] https://github.com/nodejs/node-chakracore

Re: Chromium-based Edge preview builds

#106

Post by pndy »

outside1234 wrote: post #10
saagarjha wrote: post #3

> Support for Mac and all supported versions of Windows will also come over time. Is anyone actually planning to use Edge on macOS? What reasons would you have for doing so?

Its Chrome but not Google? Sort of the same usecase as Brave?

Brave was made originally on Electron fork Muon which was recently abandoned in favor of Chromium.

Re: Chromium-based Edge preview builds

#107

Post by apocalyptic0n3 »

bendavis381 wrote: post #45
apocalyptic0n3 wrote: post #32

Earlier quoted context omitted.

Safari increasingly doesn't follow standards, implements non-standard features, and updates are tied to OS updates so if users do not update their OS (which is free on macOS but not well advertised in the OS itself), they are stuck running an old browser.

This is incorrect. Safari 12 shipped with support for macOS 10.12 and 10.13 [1]. [1] - https://developer.apple.com/safari/whats-new/

Huh. That's changed, then, since previous updates were always tied to the OS. Still not great support, though. Chrome supports back to 10.10, Firefox back to 10.9, Vivaldi back to 10.10, Brave back to 10.10, etc.

Re: Chromium-based Edge preview builds

#108

Post by Shorel »

sverige wrote: post #6

Seriously, why is MS doing this? Internet Explorer died years ago, Edge never took off, and Google isn't about to give up their market share for spyware without a fight. It's like MS thinks this is Browser Wars 3.0. Heaven help me if it turns out that MS seems to be doing something comparatively good.

Curiously, had they made Edge compatible with Windows 7 it would have had a much bigger chance of it actually being used.

The greedy strategy of wanting to have both Windows 10 and browser market share is what doomed Edge.

Re: Chromium-based Edge preview builds

#109

Post by metildaa »

ninedays wrote: post #100
metildaa wrote: post #94

Earlier quoted context omitted.

Apple will likely stick to Safari based on their Webkit fork. Look at their stewardship of coreutils and the graphics stack on MacOS, its plain to see that they just don't care if MacOS is 5+ years behind the curve on features and performance if its not hurting battety life for most users. Gaming on MacOS has become a much more limited experience than on Linux (blame Valve for this) or Windows. Apple wields a big sti…

I do not agree Valve should be to blame if Apple decided that gaming wasn't important for them. I am the first one to say when they do amazing things but the reality is that gaming never was/is a priority for Apple. Take a look at the history of OpenGL on macOS and it will become obvious that the only reason Linux today has a better support for games than Apple is Apple's fault only. I truly wish it was different.

I was blaming Valve for making gaming on Linux have such a broad library of titles. They've made Wine very easy to use, to the point that users barely know that it isn't a Linux native game.

Re: Chromium-based Edge preview builds

#110

Post by est31 »

qalmakka wrote: post #102
atombender wrote: post #97

Earlier quoted context omitted.

You're not contradicting me. The section you're quoting is not about this, by the way. You want section 2.5.2: "Apps should be self-contained in their bundles, and may not read or write data outside the designated container area, nor may they download, install, or execute code which introduces or changes features or functionality of the app, including other apps."

Yeah, but if you read carefully, section 4.7 explicitly says that you must use WebKit and JSC to run third party software. Therefore, you can use your own engine to render your app (see games or Google's Flutter), but you cannot use it to render third-party content (thus making impossible to create a browser)

Oh interesting.
Post reply on HN