User: Password:
Subscribe / Log in / New account

Google's "Blink" rendering engine

Google's "Blink" rendering engine

Posted Apr 4, 2013 5:28 UTC (Thu) by imgx64 (guest, #78590)
Parent article: Google's "Blink" rendering engine

Hopefully, this will reduce complaints about a "WebKit monoculture".

(Log in to post comments)

Google's "Blink" rendering engine

Posted Apr 4, 2013 8:22 UTC (Thu) by job (guest, #670) [Link]

Not really. It's always been an "oligoculture", where a few semi-compatible rendering engines are based on the Webkit codebase.

Web developers has always had to test against both Safari and Chrome, and both in mobile and desktop versions, since they have completely different feature sets, different css prefixes, and are built from different versions of Webkit.

The change here seems to be that Google drops a lot of Safari-specific stuff from their Webkit tree. That change was expected long ago, since Apple stated that upstream will be based around Webkit2 (which is pretty much Safari-only). Apple has never been a very considerate upstream. Something similar happened around CUPS where Linux distributions have to keep forks going.

Google's "Blink" rendering engine

Posted Apr 4, 2013 12:12 UTC (Thu) by jku (subscriber, #42379) [Link]

Saying that Webkit2 is Safari-only is not very close to the truth: Apart from chromium I can't think of a single actively maintained port that is still webkit1-based, whereas there are multiple webkit2 ports that are very much alive (even if they are having problems collaborating with Apple efficiently).

Google's "Blink" rendering engine

Posted Apr 4, 2013 12:28 UTC (Thu) by bawjaws (guest, #56952) [Link]

Any thoughts on whether those projects are likely to want to move to Chromium/Blink, and whether Google will want them to?

Google's "Blink" rendering engine

Posted Apr 4, 2013 15:06 UTC (Thu) by sumC (guest, #1262) [Link]

Opera is at least going to use Blink.

Google's "Blink" rendering engine

Posted Apr 4, 2013 21:14 UTC (Thu) by kripkenstein (guest, #43281) [Link]

In fact the timing suggests this is not a coincidence. One possibility is that Google was coordinating this in secret with Opera, so that when the Blink fork was announced it would not be just Google going alone but Google + Opera. Better PR.

Google's "Blink" rendering engine

Posted Apr 5, 2013 8:10 UTC (Fri) by khim (subscriber, #9252) [Link]

You are reading too much into this. Such things don't happen overnight. Decision to create fork most likely brewed for a long time - in fact it was a de-facto situation already (Chromium uses WebKit1 while most other direct WebKit users use WebKit2) - thus when Opera decided to join Chromium world it was probably already more-or-less decided. Which means that Opera was notified about creation of fork in advance but probably had nothing to do with decision itself.

Google's "Blink" rendering engine

Posted Apr 8, 2013 18:16 UTC (Mon) by rahvin (subscriber, #16953) [Link]

The Opera move was a cost cutting move. Opera used the "based on Chromium" announcement to cover up the layoffs of their in house staff that was maintaining their own internal rendering engine.

As I understand it almost 100 people (93 was the number I saw) got the axe with Opera's move to Chromium.

Google's "Blink" rendering engine

Posted Apr 4, 2013 17:14 UTC (Thu) by tjc (guest, #137) [Link]

Yes, it's complicated.

Google's "Blink" rendering engine

Posted Apr 8, 2013 19:11 UTC (Mon) by Los__D (guest, #15263) [Link]

"different CSS prefixes" is stretching it quite a bit: While it is true that Safari also supports legacy prefixes, both support -webkit equally.

However, the implementation of the CSS features requiring those prefixes is quite differently (esp. transforms on mobile).

Copyright © 2018, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds