Your sarcasm is well and truly appreciated but misplaced.
The idea is that these libs and framework make an honest attempt at making web apps. Also well intentioned but wide off the mark. Most people access the internet through mobile phones[1] with dodgy broadband connectivity, hence don't need an app running inside another app - do you understand the redundancy and the pitfalls of janky, horrible UIs for the marginal performance improvement? Or the famous It doesn't reload the whole page...very few people actually care about.
If you are building the next instagram, go right ahead and use bleeding edge js frameworks, but not every site/blog needs to be an app.
Except that I'm not even sure that the next Instagram or whatever should be a web app - it should be a native app.
I saw the beginning of the "write once - run anywhere" concept decades ago. Sounded fantastic. Yet here we are and it is more like "write once - stumble and crawl someplace".
It is most discouraging that many major houses do it so badly, and even their native apps are similar bloatware...
The idea is that these libs and framework make an honest attempt at making web apps. Also well intentioned but wide off the mark. Most people access the internet through mobile phones[1] with dodgy broadband connectivity, hence don't need an app running inside another app - do you understand the redundancy and the pitfalls of janky, horrible UIs for the marginal performance improvement? Or the famous It doesn't reload the whole page...very few people actually care about.
If you are building the next instagram, go right ahead and use bleeding edge js frameworks, but not every site/blog needs to be an app.
[1] https://gs.statcounter.com/platform-market-share/desktop-mob...