News for hackers. Stuff that matters.
Re:Ōryōki Web Browser by bfgeek on Wednesday June 29, 2016 @04:17PM (#12004476)
Depends on what you are counting as the "same".

Edge put together a really great visualization of the API surface of all the browsers. - https://developer.microsoft.com/en-us/microsoft-edge/platfor... The API surface (and bug surface) is actually pretty different these days.

Internally Blink and WebKit are also diverging reasonably rapidly. As a specific example here is the project to re-architect how blink does it's painting: https://www.chromium.org/blink/slimming-paint

EDIT: spelling

Re:Ōryōki Web Browser by digi_owl on Wednesday June 29, 2016 @05:18PM (#12004905)
More and more it feels that corporations have discovered that with FOSS, those that do the work get to define the standard. And thus they throw manhours upon manhours of churn at whatever market segment they hope to control.
Re:Ōryōki Web Browser by sangnoir on Wednesday June 29, 2016 @06:13PM (#12005198)
> More and more it feels that corporations have discovered that with FOSS, those that do the work get to define the standard

Not quite - those that employ the maintainers define the standard, as shown multiple times by Red Hat (multiple projects) and by Apple with WebKit.

IIRC, before the Blink fork, Google was pushing more commits into WebKit compared to Apple, but there was a - let's call it a difference in perspective - on a feature a Google employee wanted to implement, someone with an @apple.com email said "no". I can't remember what the issue was, but this development unfolded on webkit mailing list.

Re:Ōryōki Web Browser by digi_owl on Thursday June 30, 2016 @07:20AM (#12007771)
True. But without constant churn alternative implementations of interfaces can catch up.