3 ms·

I get that Apple shouldn't be allowed to dictate which features belong on the web, but you're just letting Google to it instead if you opt to use Chrome. Maybe

I get that Apple shouldn't be allowed to dictate which features belong on the web, but you're just letting Google to it instead if you opt to use Chrome. Maybe I don't care about PWAs (which I don't), maybe I don't feel like the majority of APIs introduced lately belongs in the browser. There's very little of what you should be able to do on the web that you could not do 10 years ago. Yes, flexbox is awesome, let's have that, so is the dialog tag. WebGL, Blutooth, USB, device memory, battery status... No, the browser doesn't need to support that.

nasso_dev 2y ago
The browser doesn't need to support WebGL?! Together with Web Audio and Web Assembly, they are exactly the kind of technologies allowing desktop-class apps like Figma to run in the trustworthy browser sandbox. I don't want to have to install more apps, and more web APIs means more things can be done inside of the browser shell without having to install software that could literally do anything on your computer (and is often hard to remove completely when you're done).