Sunday, April 14, 2013 [Tweets] [Favorites]

Code Hard or Go Home

John Siracusa:

Does Apple—and the rest of the WebKit community—have the skill and capacity to continue to drive WebKit forward at a pace that matches Google’s grand plans for Blink? The easy answer is, “Of course it does! Apple created the WebKit project, and it got along fine before Google started contributing.” But I look at those graphs and wonder.

[…]

This all sounds great on paper, but in (several years of) practice, Google’s Chrome has proven to be far more stable and resilient in the face of misbehaving web pages than Apple’s WebKit2-based Safari. I run both browsers all day, and a week rarely goes by where I don’t find myself facing the dreaded “Webpages are not responding” dialog in Safari that invites me to reload every single open tab to resume normal operation.

1 Comment

[...] has been reduced from two dimensions to one. Xcode and other apps have become less AppleScriptable. Safari has become buggy. Changes to Sync Services, without adequate replacements, broke Outlook and [...]

Stay up-to-date by subscribing to the Comments RSS Feed for this post.

Leave a Comment