4 ms·
> Every discussion about anything in Safari on HN, even if not at all related, for the last year or two has included multiple people complaining about the lack
by littlestymaar 9y ago
> Every discussion about anything in Safari on HN, even if not at all related, for the last year or two has included multiple people complaining about the lack of WebRTC.
> Now it's here and there is a new complaint /s
WebRTC is 6 years old and it's been implemented in Firefox and Chrome for 5 years now ! Since then there's plenty of other DOM API that where introduced and are not supported in webkit, for instance :
- service workers
- push API
- Fetch API
- User Timing API
- Subresource Integrity
On the JavaScript side, the JSC team has been doing a great job for the past two years, leading the way in term of performance and ES2015+ support, but on the DOM side, Safari is really lagging far behind (which is, I guess, probably because they don't want the compete with there native mobile apps).
- floatboth 9y agoFetch is supported in 10.1 (only 2 years after Firefox and Chromium!) They also already have Custom Elements v1 support, which is still in progress in Firefox. Timing and SRI they announced in this release (11). Service Workers is THE big gap, at this point it feels like they're actually very afraid of progressive web apps.
- rhinoceraptor 9y agoWasn't the original idea for the iPhone to just use web apps in place of native?
- floatboth 9y agoThat was the only way to add apps on iPhone OS 1.0, yes. Maybe they already had the App Store in mind and intended that as a stopgap, maybe the App Store was a reaction to jailbreaks and unofficial app development…