Live data from Hacker News

Progress Delayed is Progress Denied (Safari feature lag)

infrequently.org

1–10 of 31 posts

Re: Progress Delayed is Progress Denied (Safari feature lag)

#3

It is quite a racket. I don't believe they set out to actively harm the web and open standards, but when they make _such_ a killing on app store profits, it must limit the incentives and motivation to invest in Safari/WebKit

Look at webkit.org and tell me if you see evidence that apple isn’t working on it.

Re: Progress Delayed is Progress Denied (Safari feature lag)

#4
post #3

It is quite a racket. I don't believe they set out to actively harm the web and open standards, but when they make _such_ a killing on app store profits, it must limit the incentives and motivation to invest in Safari/WebKit

Look at webkit.org and tell me if you see evidence that apple isn’t working on it.

Yes, they absolutely _are_ working on it.

I appreciate that `gap` is finally supported in the context of `flex`. I appreciate that WKWebView finally supports `getUserMedia`. The compatibility lines in the graphs from TFA are not totally flat, it's true.

But still -- Apple, one of most well-resourced companies in the world, lags far behind Mozilla, a modest non-profit.

Re: Progress Delayed is Progress Denied (Safari feature lag)

#6
Interesting to note that the author never mentions one of the biggest criticisms of the Chromium project. That they keep adding so many APIs that other browser vendors are forced to follow them instead of what they want to work on. This has been less apparent on mobile because Safari has a large share but not on desktop. The chromium team is known to build things that the standards body doesn't agree on, ship it, and every other vendor is forced to support it because of Chrome's huge marketshare on desktop otherwise their browser will appear "broken". They're angry that they can't do this on mobile.

Re: Progress Delayed is Progress Denied (Safari feature lag)

#8
Also the author never really addresses if the API is needed or not, or if it provides a good experience. If Chrome has it, it is seen as a positive. Personally, i'm very happy that PWAs can't spam me with "You left something in your cart" notifications on iOS.

Re: Progress Delayed is Progress Denied (Safari feature lag)

#9
Also interesting to note, that some of those APIs are still in W3C drafts. So Chrome just went ahead and wrote its own implementation without the literal standards body agreeing or disagreeing on them. Again, this author is extremely biased and I don't think this article is an informative take for anyone.

Re: Progress Delayed is Progress Denied (Safari feature lag)

#10

Also the author never really addresses if the API is needed or not, or if it provides a good experience. If Chrome has it, it is seen as a positive. Personally, i'm very happy that PWAs can't spam me with "You left something in your cart" notifications on iOS.

So don't allow those notifications. I can easily see the existence of a catch-all deny everything by default as well. Safari on desktop happens to have this feature--showing Apple isn't categorically against its existence, as long as it doesn't help undermine their app store monopoly--will occasionally ask me for notifications and, somehow, I always deny them... maybe I have more willpower than you? Just because you have some personality flaw that prevents you from disabling a feature you don't like shouldn't mean that everyone else in the world needs to do without having that feature ever. In a world where Apple doesn't just make quality judgements on content but also makes legal judgments and even moral judgments--being so anti-porn as to be downright misogynistic with an anti-breastfeeding stance--this is a reasonable feature to exist on the web platform, and no one is forcing you to use it.
Post reply on HN