6 ms·

We are at the mercy of Google. Mozilla is a non-entity at this point, getting a fat paycheck from GOOG and spending it on inane initiatives.

gjsman-1000 5y ago
There's also Apple developing WebKit on iOS and macOS, but they are more "follower" than "innovator."
- cronix 5y ago
  They're also obstructionist and don't implement standards because they could harm the app store, like PWA.
  - dmitriid 5y ago
    There's no such thing as "PWA". There's half a dozen to a dozen disparate APIs, and every PWA proponent has their own list of what they consider PWA support. However, Safari has had support for basically everything you need for a PWA except, thank god, notifications.
    - gjsman-1000 5y ago
      For how many websites use notifications unnecessarily... I have a hard time feeling sorry for anyone complaining about how they can only do notifications from an app (which Apple could review).
      - 1_player 5y ago
        There are legitimate uses of notifications from websites, like being told from my webmail that I've received a new email. Or any other messaging service. But no, let's throw the baby with the bathwater because some blog sites ask for notifications to spam you. Apple isn't crippling PWAs because it cares about the user. They get more money if you pay for an app on their App Store. Simple as that. In every PWA thread I keep reading the same Stockholm Syndrome argument that Apple are crippling PWA to save us from the notification spam. Meanwhile I have native apps spamming me with offers.
        dmitriid 5y ago
        > Apple isn't crippling PWAs because it cares Apple isn't crippling PWAs. Once again: there's literally no such thing as PWA. It's bunch of very different standards. You decided that notifications support are a 100% must to qualify as "not crippling PWAs". Whereas to qualify as a "PWA" an "app" literally only needs two things: service workers and being able to be "installed". Everything else is just gravy.

gjsman-1000 5y ago

There's also Apple developing WebKit on iOS and macOS, but they are more "follower" than "innovator."

cronix 5y ago
They're also obstructionist and don't implement standards because they could harm the app store, like PWA.
- dmitriid 5y ago
  There's no such thing as "PWA". There's half a dozen to a dozen disparate APIs, and every PWA proponent has their own list of what they consider PWA support. However, Safari has had support for basically everything you need for a PWA except, thank god, notifications.
  - gjsman-1000 5y ago
    For how many websites use notifications unnecessarily... I have a hard time feeling sorry for anyone complaining about how they can only do notifications from an app (which Apple could review).
    - 1_player 5y ago
      There are legitimate uses of notifications from websites, like being told from my webmail that I've received a new email. Or any other messaging service. But no, let's throw the baby with the bathwater because some blog sites ask for notifications to spam you. Apple isn't crippling PWAs because it cares about the user. They get more money if you pay for an app on their App Store. Simple as that. In every PWA thread I keep reading the same Stockholm Syndrome argument that Apple are crippling PWA to save us from the notification spam. Meanwhile I have native apps spamming me with offers.
      - dmitriid 5y ago
        > Apple isn't crippling PWAs because it cares Apple isn't crippling PWAs. Once again: there's literally no such thing as PWA. It's bunch of very different standards. You decided that notifications support are a 100% must to qualify as "not crippling PWAs". Whereas to qualify as a "PWA" an "app" literally only needs two things: service workers and being able to be "installed". Everything else is just gravy.