4 ms·

Out of Edge/Firefox/Chrome/Safari, Safari is the furthest behind in functionality and still has the most bugs. How do we know? We develop for these browsers ev

Out of Edge/Firefox/Chrome/Safari, Safari is the furthest behind in functionality and still has the most bugs. How do we know? We develop for these browsers every day. As for "only works in Chrome", Safari was our primary target platform. We develop with a "Safari first" process (a device that live updates on changes). If the feature/functionality didn't work in Safari, for us it might as well not exist. As a user, you are not the one that has to invest 100's of hours fixing platform bugs. If a website does break, you'd blame the website even if Safari was at fault. It's also hard for any end-user to see the absence of functionality, or a useful application that never got built because it was too difficult or didn't have the underlying functionality required. It's hard to see an application that was only ever built for iOS because the costs of producing two native apps was too high, or the app that never got built at all. It's hard to see the increase in prices because of no competitive pressure on the native ecosystems, or a new mobile ecosystem that never got built because it didn't have access to apps users's wanted. At the end of the day this all ends up harming the user.

dmitriid 4y ago
> Out of Edge/Firefox/Chrome/Safari, Safari is the furthest behind in functionality Of course it hasn't. Because in your mind "functionality" is "whatever Chrome ships". And if you pretend that Edge is a separate browser, then Chrome on iOS is a separate browser. > If a website does break, you'd blame the website even if Safari was at fault. There are about zero websites that a user visits daily that break in Safari. Of those that do break yet another near zero are those that break more than some visual glitch. And of those that have significant functionality broken ... about 99% of those on a yet another Chrome-only non-standard. > It's also hard for any end-user to see the absence of functionality, or a useful application that never got built because it was too difficult or didn't have the underlying functionality required. This bullshit argument has a very good counter-argument that trumps everything you pretend is true: https://news.ycombinator.com/item?id=34907860 https://news.ycombinator.com/item?id=34907860 > At the end of the day this all ends up harming the user. At the end of the day what you think harms the user has about zero relevance. Because people bemoaning Safari's perceived deficiencies rarely know what actual real breathing users want: https://news.ycombinator.com/item?id=34517503 https://news.ycombinator.com/item?id=34517503 (and of course browser vendors have no intention of giving us that)

dmitriid 4y ago

> Out of Edge/Firefox/Chrome/Safari, Safari is the furthest behind in functionality Of course it hasn't. Because in your mind "functionality" is "whatever Chrome ships". And if you pretend that Edge is a separate browser, then Chrome on iOS is a separate browser. > If a website does break, you'd blame the website even if Safari was at fault. There are about zero websites that a user visits daily that break in Safari. Of those that do break yet another near zero are those that break more than some visual glitch. And of those that have significant functionality broken ... about 99% of those on a yet another Chrome-only non-standard. > It's also hard for any end-user to see the absence of functionality, or a useful application that never got built because it was too difficult or didn't have the underlying functionality required. This bullshit argument has a very good counter-argument that trumps everything you pretend is true: https://news.ycombinator.com/item?id=34907860 https://news.ycombinator.com/item?id=34907860 > At the end of the day this all ends up harming the user. At the end of the day what you think harms the user has about zero relevance. Because people bemoaning Safari's perceived deficiencies rarely know what actual real breathing users want: https://news.ycombinator.com/item?id=34517503 https://news.ycombinator.com/item?id=34517503 (and of course browser vendors have no intention of giving us that)