Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Also everyone complaining about mobile Safari is leaving out the parts where it excels — speed and battery life. Safari is the best browser looking at actual websites.

Safari is the reason I bought an iPhone because using Chrome on a flagship Android phone compared to Safari was night and day. Pages would load in milliseconds not seconds and scrolling and zooming didn’t stutter.

I really don’t want Apple to lose this fight and live in a world where you can’t use non-chrome browsers without dealing with broken websites.



About the broken websites.

Firefox handles most of the site perfectly `without special treatments`. It you develop a website against it, it will about 98% work on chrome, and the reverse also hold.

The safari... on the other hand is a terrible s*t. If you try to develop against other browser. Your site will break on it about 4 in 5 even only use old feature that ie11 supports.

Its web standard support is a total joke in my opinion.

It isn't really a excuse to ship a browser that is so broken. Given the small mozilla handles mostly fine with it.

How on the earth a such giant company can't?


Google took WebKit and diverged. Why should Apple have to run after it? Just because they’re big?

Devs mostly failed to realize both were WebKit, targeted chromium and not WebKit, allowing breakage and letting Google get away with it. Devs is more giant than Apple. What’s devs excuse?


I mean they failed css2 (exists since 2000) features that exists since forever and bugged even before the divergence. Those features works on literally everyone includes ie 11 except safari and even against the spec apple provided itself. They never got fixed. There are tons of obvious ancient bugs on the safari exists are since day one and seems no one it fixing it(even they confirm it is a bug on their bug tracking site). Its supports site is a total joke. This is also what I believe why the divergence happened.

If a bug exists in half of browsers and spec don't really defined it, then it's my fault.

If a bug exists in exactly one browser and behaved contrary to the spec, then it's browsers fault. And there are way too many to count on safari.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: