6 ms·
Um, no. Just look at sites like caniuse.com and see how much farther ahead Chrome and Firefox are than Safari iOS. Safari iOS has become this generations IE 6.
by irrational 10y ago
Um, no. Just look at sites like caniuse.com and see how much farther ahead Chrome and Firefox are than Safari iOS. Safari iOS has become this generations IE 6. It is seriously holding back the web. And worst of all it really only gets one update a year!
- Analemma_ 10y agoIt is possible for one's utility function on web browsers to weight speed and power consumption more than standards compliance.
- trome 10y agoWebRTC and many other major features are still missing from Webkit on iOS, whereas in Chrome & Firefox I can have a full WebRTC client on mobile.
- abalone 10y agoThat's consistent with the parent comment. They're working on WebRTC.[1] Possibly they're making it power efficient first and then shipping, as opposed to shipping and then making it efficient. [1] https://webkit.org/status/#specification-webrtc https://webkit.org/status/#specification-webrtc
- abalone 10y agoAnd Chrome is reportedly more of a battery hog on macOS[1][2] and Windows[3]. So there you go: different priorities. [1] http://www.techrepublic.com/article/browser-wars-is-chrome-or-safari-better-for-your-mac/ http://www.techrepublic.com/article/browser-wars-is-chrome-o... [2] http://www.theverge.com/2015/4/10/8381447/chrome-macbook-battery-life http://www.theverge.com/2015/4/10/8381447/chrome-macbook-bat... [3] https://www.extremetech.com/computing/230583-microsoft-claims-edge-delivers-70-more-battery-life-than-chrome https://www.extremetech.com/computing/230583-microsoft-claim...
- solidr53 10y ago[1] is not good article, no test, no numbers. [2] neither is this. no info about the test other than the results. just knowing that chrome rendered flash by default at the time of this article, i know its irrelevant. [3] claims 70%...
- abalone 10y agoFalse. From [2]: "The native Safari made the new Retina machine look good: 13 hours and 18 minutes. Google’s Chrome, on the other hand, forced the laptop to tap out at 9 hours and 45 minutes."
- jacobolus 10y agoAnecdotally, Chrome uses dramatically more memory and CPU than Safari for me (note: I typically have 100+ tabs open at once), and gives me somewhere between half and two thirds the battery life, for the same type of use. I have flash turned off for both and most ads blocked via /etc/hosts, so there shouldn’t be anything especially unfair in the results. Google web apps (gmail, google maps, etc.) seem to be a particular offender.
- jalfresi 10y agoIt's not holding back the web, settle down! It can still render websites perfectly fine and will continue to do so. Seriously, what horse are you backing where iOS Safari is compared to IE6?!? What oh-so important feature you simply must-have, that would even begin to signify that iOS Safari is "holding back the web"? The web dev world is absolutely mental at the moment...
- manigandham 10y agoThere are a lot of quirks with Safari that are similar to the way IE6 eventually stopped following standards. That fact that localstorage doesnt work in private mode is 1 example.
- kevinchen 10y agoWhere is the W3C standard for private browsing mode?
- enragedcacti 10y agoThere isn't one, that's why it should behave like a normal browser (from the web dev perspective) even while in private mode.
- abalone 10y agoThat doesn't follow. If it literally behaved like a normal browser that would break the privacy guarantee of private mode. In fact you could argue that browsers that implement localStorage in private mode are the ones who are not standards compliant. From the Web Storage spec: "[localStorage] is designed for storage that spans multiple windows, and lasts beyond the current session."[1] Thus if a browser is discarding localStorage prior to the end of the current session, it's explicitly against the spec. This is more than academic. If apps aren't written to explicitly use ephemeral storage then they may not function as expected in private mode, like, say, unexpectedly causing data loss. [1] https://www.w3.org/TR/webstorage/ https://www.w3.org/TR/webstorage/
- Gelob 10y agoSafari has so much better HLS video streaming support on iOS then chrome. Chrome has caught up a little bit but the documentation still sucks.
- irrational 10y agoUh, duh? That's because HLS is not a web standard and never will be so nobody else is going to bother building it into their browsers. The standard (ISO/IEC 23009-1:2012) way to do adaptive bitrate streaming is MPEG-DASH.
- realityking 10y agoMicrosoft Edge and Chrome on Android both support HTTP Live Streaming.
- IMcD23 10y agoNot sure if you're serious about 1 update per year...iOS has ~4 major releases per year. (9.0, 9.1, 9.2, 9.3). Safari receives updates in each one. iOS 10.3, which is in beta, comes with tons of Safari changes.
- coldtea 10y ago>Safari iOS has become this generations IE 6 Yeah, the kind of "IE6" that beat Chrome and Firefox last year to be the first to fully support ES6 for example. https://twitter.com/webkit/status/728643624464883712 https://twitter.com/webkit/status/728643624464883712 Check http://caniuse.com/#compare=chrome+59,safari+TP http://caniuse.com/#compare=chrome+59,safari+TP yourself, and you see the differences in scores is mostly because they give 1 point to every API, however non-important it is. Meanwhile, Chrome supports some good ones (File Storage, WebRTC, Pointer Events etc), but Safari supports some good ones that Chrome doesn't too: MathML, HTTP Live Streaming, Video and Audio Tracks, SVG fonts. But Chrome also tries to push various proposals of (mainly) theirs, down everyone's throats.
- irrational 10y agoMathML has been dead for years. HTTP Live Streaming (HLS) is not part of the spec and never will be. What is part of the spec is MPEG-DASH. But, File Storage, WebRTC, and Pointer Events? Those are actually useful for modern web development.
- hutzlibu 10y ago"But Chrome also tries to push various proposals of (mainly) theirs, down everyone's throats." Never experienced that with chrome, but I developed a kind of hate towards mozilla, for forcing IndexedDB and IndexedDB ONLY and refusing for anything else and therefore killing FileAPI and WebSQL