3 ms·
I think both Chrome and Safari have negative connections with memories of IE. For Safari it's the stagnation of IE6: installed everywhere but rarely updated wit
by untog 7y ago
I think both Chrome and Safari have negative connections with memories of IE. For Safari it's the stagnation of IE6: installed everywhere but rarely updated with new features that other browsers have.
That's not so much of a problem on desktop because people can always install another browser, but on iOS you're literally not allowed to use any other browser engine.
- qubex 7y agoThe issue is that major updates to Safari follow the same cycle as updates to the MacOS and iOS operating systems, meaning once per year at the current rate. Adding major features once per year (and even then, only once they have been in use on other platforms for at least a year or two) means that Safari can lag by three years in terms of features (case in point: WebRTC).
- microcolonel 7y ago> means that Safari can lag by three years in terms of features (case in point: WebRTC). In the case of WebRTC, it's even worse than that: public stable releases of Firefox and Chrome supported WebRTC by early 2013, but Safari took until late 2017. That's more than five years for an extremely popular feature (I had three professional engagements where we had to integrate a native WebRTC client component into a Cordova application, and couldn't support that feature on iOS through the browser, before they finally released it).