3 ms·

The success of the GUI shows why computing is not driven by concerns over efficiency. PWAs being less efficient than native apps is completely irrelevant. What

The success of the GUI shows why computing is not driven by concerns over efficiency. PWAs being less efficient than native apps is completely irrelevant. What matters is functionality. Most apps do nothing that requires being native at all. The fact that PWAs have been implemented badly so far does not mean that there's anything inherently ugly, slow, or less accessible. Apple could go as far as they want in making PWAs and native apps feel completely identical. They could even go as far as enforcing style, performance, and accessibility rules for PWAs. The benefit of moving to PWAs are many and the downsides are all solvable.

redial 9y ago
> Apple could go as far as they want in making PWAs and native apps feel completely identical. They could even go as far as enforcing style, performance, and accessibility rules for PWAs. But they have gone as far as they want, you should be happy then, or do you mean as far as you want? And isn't one of the points of web apps to not be enforceable by any single entity? > The benefit of moving to PWAs are many and the downsides are all solvable. Solvable only with hundreds of millions of dollars of investment and many many years of development. On second thought, they've had all that and are still not even close.