Hacker News Reader

Comment by whitehat2k9 | Hacker News Reader

It's funny that unpaid developers who release ROMs for my Android phone apparently do a better job at QA than the people at Apple.

View on HN

And of course I get downvoted for being perfectly right. The rampant, rabid Apple fanboyism on HN is utterly disgusting.

That might sound snarky, but actually it's entirely true. Apple QA around Safari is dreadful. They literally break the rendering of thousands of websites in 9.2 and only fix it in 9.3 - three months later. All because of checked in WebKit code that wasn't reviewed correctly.

https://bugs.webkit.org/attachment.cgi?id=268394&action=diff

Oh, and I should note: I love my iPhone and iPad - I own three iPads and 4 iPhones. So lest anyone think I'm an Apple hater, think again. In fact, I replaced my Windows PC with a Mac some time ago and never looked back.

Which is why I'm hear to tell Apple: fix your freakibg regressions in Safari quickly. There is absolutely no reason why the browsers rendering engine can only be updated every three months!

Sort it out Apple. You force all web apps to use your engine and prevent effective completion in this space: fine. But you now face the burden on ensuring you prevent and fix your bugs quickly!

I do find it odd that Safari's update cycle is tied to the OS updates. Seems to me like they should be separate.

Example: a few months ago Safari had a bug where it was still using apple's old WWDR certificate, preventing anyone from packaging their safari extensions. The fix came out months later in the next OS release.

You have 3 comments in this thread stating that this wasn't reviewed correctly. It was, you're just looking at the wrong link in their bugtracker: http://trac.webkit.org/changeset/194667 "Reviewed by Tim Horton."

You are the one who is mistaken, not me. I never said the revert wasn't reviewed, and neither did Simon Fraser. What he said was the commit that caused the viewport bug that made its way into iOS 9.2 wasn't reviewed.

That clear enough for you now?

Still not clear to me -- is this the checkin that caused the issue -- reviewed by Tim Horton? http://trac.webkit.org/changeset/186786

Ah. I'm an idiot. I guess I can only apologise for my tone and response. Sadly it has affected my larger point, but the only one to blame here is myself.

Sorry :-(

Reply on news.ycombinator.com