[lucid00]

The "Safari is the new IE" article was about them being slow to adopt APIs and the yearly release cycle attached to OS updates.

This is about visuals and UI based APIs that can be polyfilled. They matter but not as much as stuff like WebRTC and Service Workers IMO.

Google can fix these problems with updates and polyfills. Apple can't do that. Some iOS and Mac OS users will at some point be left out.

Nothing in this article matter that much "position:sticky, no backdrop-filter, no scroll-snap-type, gradients" they're useful, but not critical.

Doubt we'll see apps that aren't possible without these. They just make the experience nicer, they don't make products happen though.

Meanwhile on the Chrome end we've got web apps like Emojoy (https://jakearchibald-gcm.appspot.com/), Offline Wikipedia (https://wiki-offline.jakearchibald.com/), Instant.io (https://instant.io/), PeerCloud (https://peercloud.io/) and even Facebook (http://Facebook.com/) all providing features and services in Chrome (WebRTC, Service Workers, Background Sync) that can't be polyfilled or will have to provide a far lesser experience in Safari because it lacks even a way to polyfill these features (only things I can think of are AppCache and WebSockets which don't get the job done for these services).