Linked by Thom Holwerda on Mon 8th Apr 2013 16:59 UTC
Internet & Networking Peter Bright has summarised some of the post-fork discussions on the WebKit mailinglists. "Now that Google is going its own way and developing its rendering engine independently of the WebKit project, both sides of the split are starting the work of removing all the things they don't actually need. This is already causing some tensions among WebKit users and Web developers, as it could lead to the removal of technology that they use or technology that is in the process of being standardized. This is leading some to question whether Apple is willing or able to fill in the gaps that Google has left." There's a clear winner and loser here.
Thread beginning with comment 557961
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Different question?
by Radio on Mon 8th Apr 2013 18:46 UTC in reply to "Different question?"
Radio
Member since:
2009-06-20

All wrong. In the example presented in the article, the technology isn't abandonned by Google, they keep it in Blink and it is on the way to becoming a standard.

It is Apple engineers who are close to causing fragmentation by mindlessly abandoning this future standard css property.

Edited 2013-04-08 18:46 UTC

Reply Parent Score: 3

RE[2]: Different question?
by jared_wilkes on Mon 8th Apr 2013 18:58 in reply to "RE: Different question?"
jared_wilkes Member since:
2011-04-25

Nonsense. The article takes the stance that if these organizations choose to stay with WebKit, that Apple may abandon them... which itself is nonsense. If these organizations go with Blink, then neither Apple nor these organizations have a webkit problem.

Reply Parent Score: 2

RE[3]: Different question?
by Thom_Holwerda on Mon 8th Apr 2013 19:08 in reply to "RE[2]: Different question?"
Thom_Holwerda Member since:
2005-06-29

If these organizations go with Blink, then neither Apple nor these organizations have a webkit problem.


Considering Apple's contributions to WebKit were tapering off substantially - contributors leaving WebKit will be a MAJOR problem for Apple if they don't step up their game.

I'm sure they will, but saying Apple doesn't have to do a thing is clearly false.

Reply Parent Score: 6

RE[2]: Different question?
by jared_wilkes on Tue 9th Apr 2013 00:43 in reply to "RE: Different question?"
jared_wilkes Member since:
2011-04-25

The example you are referencing is only in Chromium. It's recent, beta code of a beta feature. Apple is not responsible for supporting this code. Intimating that it is is nonsense. Safari (on desktop and mobile) has always been competitive and a good exemplar of a browser provider in supporting and improving CSS (both when it led and when it followed in supporting new standards).

Reply Parent Score: 2

RE[3]: Different question?
by phoudoin on Tue 9th Apr 2013 10:29 in reply to "RE[2]: Different question?"
phoudoin Member since:
2006-06-09

The example you are referencing is only in Chromium. It's recent, beta code of a beta feature. Apple is not responsible for supporting this code. Intimating that it is is nonsense. Safari (on desktop and mobile) has always been competitive and a good exemplar of a browser provider in supporting and improving CSS (both when it led and when it followed in supporting new standards).


Yes, it had *because* the engine behind was the same: webkit.

Now that pretty much all WebKit contributors but Apple are shifting elsewhere/leaving it, nobody will keep WebKit moving forward supporting and improving its feature sets if Apple don't step in.
And if the graph shows something, it's that up to 50% of last one or two years's improvements made on webkit was not from Apple.

They lost half of the horse power behind the web engine powering internet user experience on their products and, worse, the half one that was working for free, as in speech *and* beer - from Apple's PoV.
That's the price for trademarking "webkit".
Nice job, Cupertino's guys.

Now, put your money where your mouth is: webkit is now *yours*. Only *yours*.
Enjoy it or abandon it, I really can't care less.

Edited 2013-04-09 10:33 UTC

Reply Parent Score: 3

RE[3]: Different question?
by lucas_maximus on Thu 11th Apr 2013 21:28 in reply to "RE[2]: Different question?"
lucas_maximus Member since:
2009-08-18

As a Web Developer, Safari is a fucking piece of shit that I rarely bother testing on.

* There was a bug in version 5 where it just would just stop downloading images/css/js for no apparent reason. There was never a fix in 2 years.

* HTML 5 Video support on Windows Requires Quicktime.

* Developer Tools are hidden away and cannot be launched by a keyboard shortcut (F12 on every other browser).

* Windows Versions of Safari would render differently than Mac Versions.

I am sure there is some that I have forgotten.

Reply Parent Score: 2