> How can you build engaging web applications if you are not even allowed to rely on standards like JS (e.g. if the user turns off JS)? I think it skews the co

> How can you build engaging web applications if you are not even allowed to rely on standards like JS (e.g. if the user turns off JS)? I think it skews the conversation to talk about JS being "turned off", rather than unavailable, as it assumes that every user agent (browsers, screen readers, crawlers, CLI commands, etc.), even those cobbled together 5 minutes ago to do one quick job, is capable of running JS, has a DOM, is up to date, implements various APIs, that those APIs even make sense (what's the screen resolution of wget running in an SSH session?); and that the user has manually told it not to.