5 ms·
Hey Apple, how about developing your browsers to support modern web technologies first?
by mbrookes 10y ago
Hey Apple, how about developing your browsers to support modern web technologies first?
- Benjamin_Dobell 10y agoThe latest Safari release is actually ahead of the game in a lot of areas. I don't run it as my primary browser still, but it does look like at least someone within Apple cares.
- proyb2 10y agoIsn't Safari Technical Preview supported 100% ES6? https://news.ycombinator.com/item?id=11708840 https://news.ycombinator.com/item?id=11708840
- saurik 10y agoApple definitely keeps up with core JavaScript and CSS support, but essentially anywhere the web undermines their attempt to maintain control over a protocol, file format, or API--or for anything that makes the browser fundamentally more powerful (which undermines their attempt to get developers to focus on native applications, and which stuff like ES6 is fundamentally not an example)--they invest only a token amount of effort at best and at worst they seem to actively cause more fragmentation (by pushing Safari-only proprietary and sometimes even patent-encumbered alternatives).
- paulddraper 10y agoHave you examples?
- saurik 10y agoService Workers, Pointer Events, Web Notifications, WebRTC... I could probably go on, but these are the ones everyone generally has at the top of their heads and which I can just rattle off without thinking about it much (and which have already been mentioned by other people on this very threads, and so absolutely should not require listing :/). The story of IndexedDB vs WebSQL (with Safari developers apparently being extreme zealots for the latter and essentially refusing to implement the former for years) is another great example. I recommend doing some basic searches using Google, as there is tons of great commentary on how Safari is "the new IE6" or is simply holding back the web.
- paulddraper 10y agoFirefox was just the opposite on Indexed DB/WebSQL. History written by the victors.
- saurik 10y agoWebSQL was never going to be picked up by Microsoft either: it was a WebKit-only concept that was doomed from the start.
- paulddraper 10y agoOpera might disagree.
- xxs 10y agoOpera is WebKit based, so your remark is not well placed.
- gcp 10y agoIt was a SQLite only concept, not so much a WebKit only concept. Of course defining the API for years to come based on the quirks of one particular implementation was terrible, even if somewhat convenient at the time.
- gcp 10y agoFirefox argued that WebSQL was a terrible idea that shouldn't become a standard, and the other vendors eventually agreed, including some that were already shipping it.
- paulddraper 10y agoRight. "[Firefox] developers apparently being extreme zealots for [IndexedDB] and essentially refusing to implement [WebSQL] for years"
- 10y ago
- Yaggo 10y agoNot only Technology Preview, but already released Safari 10 is currently the only 100% ES2015 (ES6) compliant browser. https://kangax.github.io/compat-table/es6/ https://kangax.github.io/compat-table/es6/
- madeofpalk 10y agoLike?
- sparkling 10y agoWebM and WebP support
- astrange 10y agoNot supporting WebP would be a mercy. They just let the Xvid guy working at Google release the first version of their codec as an image format, and now they can't update it. I recommend supporting ffv1 or HEVC Still Profile (where patents don't apply).
- Geee 10y agohttp://iswebrtcreadyyet.com/ http://iswebrtcreadyyet.com/ Obviously Safari wouldn't matter if Apple allowed other browsers on iOS, but no, they insist on dragging the whole Internet a few years behind.