News for hackers. Stuff that matters.

A comment on Apple is not defending browser engine choice. Parent comment

Re:Apple is not defending browser engine choice by js4ever on Friday June 24, 2022 @03:45AM (#31858816)
Maybe it's because so many things are either not working (web rtc, push), intentionally broken (PWA), or not available at all on safari.

From my point of view, safari is the IE of modern times.

[ Parent | on HN ]
Re:Apple is not defending browser engine choice by masswerk on Friday June 24, 2022 @04:38AM (#31859121)
> So many things intentionally broken (PWA)

Mind that PWA are, as it now, as Mozilla has pulled out, pretty much a Chromium-only thing.

[ Parent | on HN ]
Re:Apple is not defending browser engine choice by resoluteteeth on Friday June 24, 2022 @06:58AM (#31860012)
Only on desktop
[ Parent | on HN ]
Re:Apple is not defending browser engine choice by dmitriid on Friday June 24, 2022 @05:46AM (#31859592)
> intentionally broken (PWA)

People keep saying at as this is the truth.

1. There's no such thing as PWA. It's an umbrella term for nearly a dozen different standards

2. I think push notifications were the only ones missing from iOS Safari, so what exactly is "intentionally broken"?

[ Parent | on HN ]
Re:Apple is not defending browser engine choice by the_gipsy on Friday June 24, 2022 @09:12AM (#31861213)
Push notifications is THE most important feature preventing companies from building webapps instead of multiple native apps. This is not a coincidence, as native apps bring revenue and drives platform establishment. Push notifications have been available on Android for a decade.

As a user, this is really disappointing, especially when apple boast about "putting the user first" in matters of privacy. Native apps are much more privacy invasive than webapps.

[ Parent | on HN ]