While it’s just one small section of the article, I notice there is the sort of industry-standard erasure of the entire concept of good vs bad UI or engineering, in the “Web apps are bad” section.

A “good” app, in this article, is one that is “successful, versatile, [or] capable.” Any McDonald’s kiosk is an example of a “good” app, because it’s so “successful.” If you think a much-used app has UI that isn’t “good” and would be improved by using native technologies, well, first of all, “the market” is the arbiter of what’s good, not you, and second of all, even if you are right, your criticism lacks empathy for the “requirements and constraints” developers face, you are ignorant about the fact that things have tradeoffs, or you are some perfectionist who thinks everything needs to be a work of art.

Software engineers are so preemptively defensive about quality.