3 ms·

> It has nothing to do with creating a user friendly experience. This is absolutely not true. Think about any kind of dynamic dashboard or data management plat

> It has nothing to do with creating a user friendly experience. This is absolutely not true. Think about any kind of dynamic dashboard or data management platform. Having full page reloads for any minor change to filters, etc, is simply an unacceptable UX. But it has to be web-based because you need to be able to access it from any device, anywhere, without installing an app. Plus, on a personal level, there are many services for which I will never install a native app—because I don't use it often, or because the native app provides no added benefit, or for one of a hundred other reasons. Those services don't get my business if they don't have a web app.

dredmorbius 7y ago
That is a significant, but limited-use, case. Theere's no reason a static contnt page must require JS Simply to render text, with a blank page as fallback. Better ways of addressing the dashboaard example might be worth considering. Too: bullshit dashboards with JS-based fakery; https://www.theverge.com/2016/11/8/13571216/new-york-times-election-forecast-jitter-needle https://www.theverge.com/2016/11/8/13571216/new-york-times-e...
- RussianCow 7y ago
  Limited? That describes about half the applications I've built in my career! In all seriousness, there is a big difference between static content pages and full-blown applications; the cost to make the latter work properly without JS enabled is almost never worth it. But the same is true even for some static pages; for instance, I would never expect that NY times election forecast page to work without JavaScript, and don't see any reason that it should. (The "JS-based fakery" is pretty irrelevant to the discussion, IMO.)
  - dredmorbius 7y ago
    What fraction of all HTML pageloads? And: Sampling bias. A simple static page shouldn't require development. Hence, anyone doing web dev will have experience skewed strongly to more complex designs. How would you describe the basic underlying structure and mechanics of a typical app you've built?

dredmorbius 7y ago

That is a significant, but limited-use, case. Theere's no reason a static contnt page must require JS Simply to render text, with a blank page as fallback. Better ways of addressing the dashboaard example might be worth considering. Too: bullshit dashboards with JS-based fakery; https://www.theverge.com/2016/11/8/13571216/new-york-times-election-forecast-jitter-needle https://www.theverge.com/2016/11/8/13571216/new-york-times-e...

RussianCow 7y ago
Limited? That describes about half the applications I've built in my career! In all seriousness, there is a big difference between static content pages and full-blown applications; the cost to make the latter work properly without JS enabled is almost never worth it. But the same is true even for some static pages; for instance, I would never expect that NY times election forecast page to work without JavaScript, and don't see any reason that it should. (The "JS-based fakery" is pretty irrelevant to the discussion, IMO.)
- dredmorbius 7y ago
  What fraction of all HTML pageloads? And: Sampling bias. A simple static page shouldn't require development. Hence, anyone doing web dev will have experience skewed strongly to more complex designs. How would you describe the basic underlying structure and mechanics of a typical app you've built?