4 ms·
No need to even go this far. Just have Javascript as an option, not a default. People seem to have lost sight of the fact that the web was and still is functi
by 1vuio0pswjnm7 5y ago
No need to even go this far. Just have Javascript as an option, not a default. People seem to have lost sight of the fact that the web was and still is functional without all the added browser features. By all means, have the features, but making them defaults is something very different. It is denying the more basic functionality of the web. In some (read: many) cases, using the web in a more basic way without certain features reduces the amount of risk a user undertakes. Sometimes it is just plain faster and more reliable, too.
This developer-dictated "defaults" strategy is developer-friendly but user-hostile; it's why we end up with power users commenting on HN along the lines of "I can't turn off X, because then all sites will break." Most users (non-power users) cannot even turn off X because they do not even know they can. They haven't got a clue. Developers like it this way. This is some highly manipulative maneuvering; this is unethical IMO, but I think like a user not a developer.
Defaults are definitive. Perhaps that's why the current CEO of Google, before he became CEO, worked so intently to get vendors to make Google the "default search engine". Users do not change these defaults.
- enriquto 5y ago> Just have Javascript as an option, not a default. This is already the case, isn't it? You can easily disable js for good, and then enable it as needed on a per-site basis.
- SkeuomorphicBee 5y agoIt hasn't been the case for some time now. JS started as something to spice up the html content, to add extra niceties. But The rise of virtual Dom JS rendering Frameworks brought upon pages that don't have any html content, that don't display anything without JS, Just a Blanc page. For some time adopters of such Frameworks would keep a limited functionality noscript page, but it didn't take long for them to drop the extra work. The highest profile website following this theme is Twitter, the dropped noscript a year ago. So JS is not optional anymore, to browse the full web you need JS, without it you get a subset that doesn't include some major social networks or some major news sites.
- sergiomattei 5y agoIt is an option, the web has just evolved past no-javascript sites.
- alpaca128 5y agoOr in other words, it's actually not an option. You disable JS, you make most websites unusable out of the box. You don't even need to go that far; disable web fonts and half the websites' buttons become undecipherable. Technically those might be options, but in reality you have no other choice if you want to use the web.
- cout 5y agoI would like to see something in the middle. Instead of defaulting to no javascript, default to "javascript lite". But make "javascript lite" full-featured enough that it makes building websites _easier_. I know a lot of people have tried this already, so clearly it's a hard problem, but I think there's a market for it. There's a reason why wordpress, geocities, myspace, medium, and even AMP all exist. Limiting a content creator's options can make things simpler, and people want simple. Imagine a technology where I can test my page on one browser and be confident it looks right everywhere, not because the browser has market dominance, but because all the hard work of targeting the lowest common denominator has already been done for me. When was the last time you thought "hmm I better check and make sure this markdown document renders correctly in safari"? I think this is where the world is heading, and it's why so many sites are supporting markdown syntax. But there are so many markdown flavors and engines that we've just pushed the problem to a different level of the tech stack. But I think the concept is sound, even if the technology is still evolving toward that ideal.
- yurishimo 5y agoWhat you’re describing is/was jQuery. Then we learned how to transpile things back to earlier versions of JS and all bets were off. If you use today’s jQuery to build out some functionality today, it will likely work exactly the same for every browser since IE10.
- 5y ago