6 ms·
No, it should be the developer's job to make content accessible in the most efficient way and to the widest audience. JS can be, but often it really shouldn't b
by userbinator 7y ago
No, it should be the developer's job to make content accessible in the most efficient way and to the widest audience. JS can be, but often it really shouldn't be used and there is a simpler solution. Some sites really do need to be JS webapps, but most of them don't. Your users may not care whether you use JS or not, but they do care when your site is slow because you chose to "appify" it unnecessarily and make it require downloading and running JS to show the same content that could've been directly served as a static HTML page.
- todd3834 7y agoI would argue that the developer’s job should be to determine whether or not supporting users without JavaScript would generate more money than it costs to maintain. It’s going to depend on the target audience and what you are developing. For example: Google Docs with JavaScript turned off makes no sense to me. Hacker News on the other hand could make sense. Much higher percentage of security concerned users and the amount of work to support it is likely not monumental.