[Bilal_io]

> I may be in the minority but, as a user, web apps on mobile is the last thing I need.

I am glad for you that you don't need them. But we'd like to at least have the choice.

> snake oil

You dislike web apps, that's okay. But you sound prejudiced.

[chkhd]

> ..you sound prejudiced.

I am providing critique here, the burden of proof is on whoever wrote the bold claim that application development is web development (speculation) and it is a better way of development (speculation).

> I am glad for you that you don't need them. But we'd like to at least have the choice.

I would not have a gripe with the article if it were the only thing it alluded to.

[Nevermark]

I think some of that "proof" goes beyond "web". I.e. there is a way to deliver apps without going through gatekeepers, but a major gatekeeper is blocking that.

Innovation being actively blocked today, includes streaming games and other apps, cloud hosted apps, etc. And we will never know how much innovation is being blocked if there is always a gatekeeper.

This innovation freeze isn't just about "web" technology. It is blocking whole business models today.

And there is no reason "web" technologies, when free to improve, can't acheive parity or near parity with native apps in the future, with regard to performance, security, aesthetics, etc.

"Web" is just a historical starting place, not an impediment to future capabilities.

[chkhd]

Open, widely adopted standards are a good thing. Widely supported ways of delivering applications written using those standards is also a good thing.

But as a counterpoint to the rest, web technologies have been free to achieve said parity on the desktop for a long time now. Have they? Do they provide _better_ experience for the user? or do they neglect the user whenever they can in return for _faster_ and _easier_ cross-platform development and ability to leverage existing web developers?

[Nevermark]

The diversity of development environments, languages, etc. that sit on top of web tech such as HTML and WebAssembly provide tools for everything from quick and dirty to highly engineered code.

For instance we have PHP (easy to learn, but weak typing, arguably unclear design philosophy) on one end of the spectrum, and Rocket for Rust (which enforces memory discipline to provide highly reliable concurrency and high performance) at the other end.