PWA is an antifeature anyway; it's an operating system inside a browser. This benefits companies that have market-dominant browsers and do not have operating systems; on a technical level it's just stupid.
I love PWAs when the alternative is Electron, I'd rather let one browser instance run my crapps since it improves memory sharing and other resource utilization.
I really like being able to install websites as apps too so my WM can manage them independently.
This is what Mozilla has to say about Web Bluetooth:
> This API provides access to the Generic Attribute Profile (GATT) of Bluetooth, which is not the lowest level of access that the specifications allow, but its generic nature makes it impossible to clearly evaluate. Like WebUSB there is significant uncertainty regarding how well prepared devices are to receive requests from arbitrary sites. The generic nature of the API means that this risk is difficult to manage. The Web Bluetooth CG has opted to only rely on user consent, which we believe is not sufficient protection. This proposal also uses a blocklist, which will require constant and active maintenance so that vulnerable devices aren't exploited. This model is unsustainable and presents a significant risk to users and their devices.
Which PWA features did Apple and Mozilla remove on security grounds? What was Mozilla’s justification? What’s your justification for claiming they lied about it and it wasn’t for security reasons?
This is a little disingenuous because Apple often falsely claims security when it’s to hold back tech that could loosen the App Store grasp.