News for hackers. Stuff that matters.
Re:Microsoft is building a Chromium browser to replace Edge ... by c-smile on Monday December 03, 2018 @10:03PM (#18595727)
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.

Re:Microsoft is building a Chromium browser to replace Edge ... by 013a on Monday December 03, 2018 @10:45PM (#18596014)
We do still fortunately have three (more or less) independent popular implementations: Google with Blink, Apple (and now Microsoft) with WebKit, and Mozilla with Gecko.

These are still three strong and independent voices; Chrome has substantial control on desktops, Apple has a stranglehold on their highly popular platforms, and Mozilla has both the hearts of the tech community as well as wide regard in bleeding edge technology with Rust, Quantum/Stylo, and Servo.

Re:Microsoft is building a Chromium browser to replace Edge ... by jcranmer on Monday December 03, 2018 @11:49PM (#18596371)
I'd put the count at 2¾: Blink counts for ½ since it's an ex-fork of WebKit. While a lot of the new feature development of the two are independent of each other, they still largely share a lot of the same architecture, which means there's going to be correlation in things like ease of implementation. The extra ¼ comes from Servo, which ends up having the opposite edge of the dichotomy from Gecko; it's effectively a ground-up re-implementation of the layout engine stack, so its internal architecture is quite different from everybody else, but it's goal isn't to drive new feature development in web standards.
Re:Microsoft is building a Chromium browser to replace Edge ... by basch on Monday December 03, 2018 @11:16PM (#18596196)
Microsoft will use Blink not WebKit. Teams and VSCode are already Electron apps.
Re:Microsoft is building a Chromium browser to replace Edge ... by Manishearth on Tuesday December 04, 2018 @02:03AM (#18597006)
Right, the point being made is that Webkit/Safari are often the slowest of the bunch which is fine when you have three others but now each browser effectively has veto power and the expectation is that Webkit will wield it often.

It's saying "oh no, now Webkit can block things", not "oh no, we don't have enough strong implementations"

Re:Microsoft is building a Chromium browser to replace Edge ... by bunnycorn on Tuesday December 04, 2018 @08:28AM (#18599209)
Since when WebKit is the "slowest of the bunch"?

WebKit's JavaScriptCore is the best performant of the big 4.

Re:Microsoft is building a Chromium browser to replace Edge ... by Manishearth on Tuesday December 04, 2018 @08:55AM (#18599405)
Slowest to implement things.
Re:Microsoft is building a Chromium browser to replace Edge ... by bunnycorn on Wednesday December 05, 2018 @05:56AM (#18607216)
WebKit was the first to fully implement ES6.

https://twitter.com/webkit/status/728643624464883712?s=21

Re:Microsoft is building a Chromium browser to replace Edge ... by Manishearth on Friday December 07, 2018 @08:03AM (#18627287)
"often" slowest of the bunch
Re:Microsoft is building a Chromium browser to replace Edge ... by TheAceOfHearts on Monday December 03, 2018 @10:14PM (#18595814)
W3C is completely irrelevant when it comes to a bunch of browser stuff. WHATWG is the standards body that matters when it comes to HTML.
Re:Microsoft is building a Chromium browser to replace Edge ... by jcranmer on Monday December 03, 2018 @11:53PM (#18596387)
Browser stuff is more than HTML. CSS, for example, is still driven by the W3C and not WHATWG.
Re:Microsoft is building a Chromium browser to replace Edge ... by pier25 on Monday December 03, 2018 @10:22PM (#18595874)
Webkit and Blink are not the same. Blink forked years ago and went their own way.

Also, Blink is only the renderer. Safari does not use V8.

Re:Microsoft is building a Chromium browser to replace Edge ... by Klonoar on Monday December 03, 2018 @10:12PM (#18595790)
Mmmm isn't this effectively Gecko/Blink/WebKit now?
Re:Microsoft is building a Chromium browser to replace Edge ... by baroffoos on Monday December 03, 2018 @11:54PM (#18596395)
Soon to be Servo
Re:Microsoft is building a Chromium browser to replace Edge ... by ngokevin on Tuesday December 04, 2018 @01:18AM (#18596825)
There’s not much work on a pure Servo browser beyond experiment. They’ve just various uplifted Servo bits like webrenderer and stylo into Gecko.
Re:Microsoft is building a Chromium browser to replace Edge ... by Vinnl on Tuesday December 04, 2018 @03:31AM (#18597502)
There's this which I'm hopeful for: Android Components [1]. If Mozilla make it easy for Android apps to use Servo as the shell for modern web apps, then the improved performance might make it worth it to "restrict" yourself to using only the features supported by Servo (i.e. without many of the workarounds that make old websites work).

[1] https://github.com/mozilla-mobile/android-components/

Re:Microsoft is building a Chromium browser to replace Edge ... by c-smile on Monday December 03, 2018 @10:14PM (#18595815)
Blink and WebKit cannot be considered as separate implementations - their codebase is in sync AFAIK.
Re:Microsoft is building a Chromium browser to replace Edge ... by saagarjha on Monday December 03, 2018 @10:18PM (#18595846)
Blink was forked a long time ago–do they still share patches?
Re:Microsoft is building a Chromium browser to replace Edge ... by alwillis on Monday December 03, 2018 @10:36PM (#18595955)
There are enough similarities that Igalia (https://www.igalia.com/) could implement CSS Grid for Blink and WebKit at about the same time.
Re:Microsoft is building a Chromium browser to replace Edge ... by fabrice_d on Monday December 03, 2018 @10:22PM (#18595876)
They share less and less. Blink did a `rm -rf third_party/Webkit` recently.
Re:Microsoft is building a Chromium browser to replace Edge ... by c-smile on Monday December 03, 2018 @10:30PM (#18595908)
Patches is not the only mechanism to keep code in sync.

For two engines forked from the same source (same architecture and even same code tree structure) it is relatively easy to copy/paste feature implementation, no?

Re:Microsoft is building a Chromium browser to replace Edge ... by om2 on Tuesday December 04, 2018 @02:10AM (#18597042)
In theory maybe, but in practice we rarely do. Sometimes even when the idea is pretty clear, like WebKit's CSS JIT, it's not that easy to copy because of underlying assumptions.
Re:Microsoft is building a Chromium browser to replace Edge ... by saagarjha on Tuesday December 04, 2018 @03:36AM (#18597535)
Just curious, what kind of underlying assumptions are required for the CSS JIT (which is completely new to me! I had no idea this even existed)? I read this: https://webkit.org/blog/3271/webkit-css-selector-jit-compile... but I didn't see anything specific (by the way, the spinning animation for the gear is broken on my Safari Technology Preview).
Re:Microsoft is building a Chromium browser to replace Edge ... by SimeVidas on Monday December 03, 2018 @10:21PM (#18595873)
This made me giggle. Google and Apple are definitely developing their respective browser engines entirely separately.
Re:Microsoft is building a Chromium browser to replace Edge ... by c-smile on Monday December 03, 2018 @10:10PM (#18595777)
Started seriously thinking about converting Sciter to full scale web browser.

Anyone is willing to invest in that?

Re:Microsoft is building a Chromium browser to replace Edge ... by buboard on Tuesday December 04, 2018 @04:50AM (#18597947)
> will be written by WebKit team alone.

or, webkit will become the equivalent of linux for browsers. Considering that there will be less incompatibilities , it's a good thing. The hope is that competition for users will lead to innovations that benefit them, and not wall them off from competing platforms.

Re:Microsoft is building a Chromium browser to replace Edge ... by zapzupnz on Monday December 03, 2018 @10:11PM (#18595781)
Chromium has greater share, so I think it would be more the Chromium team.
Re:Microsoft is building a Chromium browser to replace Edge ... by Someone1234 on Monday December 03, 2018 @10:14PM (#18595811)
How independent are Chromium from Google/Chrome? Legitimately asking.
Re:Microsoft is building a Chromium browser to replace Edge ... by kowdermeister on Tuesday December 04, 2018 @03:11AM (#18597360)
Independent enough for Microsoft to pick it up. I think this will be amazing.
Re:Microsoft is building a Chromium browser to replace Edge ... by naner on Monday December 03, 2018 @10:09PM (#18595764)
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.
Re:Microsoft is building a Chromium browser to replace Edge ... by ztjio on Monday December 03, 2018 @10:13PM (#18595797)
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 over to Chrome. Mostly I use Chrome to keep my invasive work IT staff from having access to my private browsing info.

Re:Microsoft is building a Chromium browser to replace Edge ... by qwerty456127 on Monday December 03, 2018 @10:20PM (#18595855)
The problem with Edge is it still (like IE had been always but at a small number of moments in history when it actually was the original source of an innovation) is the worst of the browsers from the standards (or non-standards, whatever) support perspective. See caniuse.com
Re:Microsoft is building a Chromium browser to replace Edge ... by naner on Tuesday December 04, 2018 @12:07AM (#18596452)
Thanks, that is what I was missing. It makes sense that Edge would be preferred on Win 10 touchscreen devices.
Re:Microsoft is building a Chromium browser to replace Edge ... by c-smile on Monday December 03, 2018 @10:12PM (#18595794)
I am using it on day per day basis. It has some problems but works for me in 99.9% of cases.
Re:Microsoft is building a Chromium browser to replace Edge ... by nl on Monday December 03, 2018 @10:49PM (#18596041)
About 12% of Windows10 users are on Edge according to this[1]. Another 6% are on IE classic.

[1] sorry for the URL: https://netmarketshare.com/browser-market-share.aspx?options...

Re:Microsoft is building a Chromium browser to replace Edge ... by vbezhenar on Monday December 03, 2018 @10:26PM (#18595892)
Is IE dead?
Re:Microsoft is building a Chromium browser to replace Edge ... by russdpale on Tuesday December 04, 2018 @08:41PM (#18605118)
Its been dead, but only now has MS finally conceited the defeat. This might be bad for the industry, but its a personal victory for many of us.
Re:Microsoft is building a Chromium browser to replace Edge ... by sureaboutthis on Monday December 03, 2018 @10:57PM (#18596082)
IE has been dead for years. Some still have to put pity on IE11 or even IE10 but we're all hoping for a rapid death.
Re:Microsoft is building a Chromium browser to replace Edge ... by sureaboutthis on Monday December 03, 2018 @10:55PM (#18596068)
It is two, not three.
Re:Microsoft is building a Chromium browser to replace Edge ... by chrisseaton on Monday December 03, 2018 @10:29PM (#18595906)
Who cares what the W3C think is a draft or a recommendation?
Re:Microsoft is building a Chromium browser to replace Edge ... by sureaboutthis on Monday December 03, 2018 @10:56PM (#18596074)
The entire internet and web development community, that's who. While WHATWG has taken over the HTML part, it's the W3C that still gets all the action everywhere else.
Re:Microsoft is building a Chromium browser to replace Edge ... by jcranmer on Monday December 03, 2018 @11:52PM (#18596380)
The experience of standards bodies has generally agreed that you can't shake out all the problems with a specification until you have at least two independent implementations.