5 ms·

Who said every site should work without JS, even Figma? Honestly, who is saying that? Who is saying these things?

gumballindie 3y ago
I think the points in this blog are made up. No one with a bit of experience “believes” such things.
diggan 3y ago
> https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=%22should%20work%20without%20js%22&sort=byDate&type=all https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... (25 results) > https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=%22should%20work%20without%20javascript%22&sort=byDate&type=all https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... (28 results) So at least some are saying something along those lines. I'm sure if you search Xitter you'll find even more hits. I think the argument is usually not made in isolation like that though, and usually with exceptions. "Websites without heavy user interaction should work without JS", "Websites should work without JavaScript, unless based on live data" and so on, which makes a lot more sense.
- draw_down 3y ago
  [dead]
croisillon 3y ago
fyi you are shadowbanned, write hn an email to clear that up
brightball 3y ago
“Every” is a bit extreme but I’ve been a believer in Graceful Degradation for years. This is where jQuery excelled.
blackoil 3y ago
A ridiculously small but very vocal minority which is active on forums like HN.
ryanbrunner 3y ago
I tend to make all my pages function without Javascript even if I don't expect my users to turn off Javascript. It makes things easier to cover with automated tests if I can just exercise my backend servers with scripts vs. a headless browser, and if something does go wrong with serving Javascript or something it's nice to know my site is functional. Generally speaking the experience will be horrible (what should be a modal or a partial page reload will be a full reload) but using the technologies I use it's not that hard and it makes my development experience easier while delivering some (rarely needed) benefits to end users, so it's an unqualified win for my particular use case.

I think the points in this blog are made up. No one with a bit of experience “believes” such things.

> https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=%22should%20work%20without%20js%22&sort=byDate&type=all https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... (25 results) > https://hn.algolia.com/?dateRange=all&page=0&prefix=true&query=%22should%20work%20without%20javascript%22&sort=byDate&type=all https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que... (28 results) So at least some are saying something along those lines. I'm sure if you search Xitter you'll find even more hits. I think the argument is usually not made in isolation like that though, and usually with exceptions. "Websites without heavy user interaction should work without JS", "Websites should work without JavaScript, unless based on live data" and so on, which makes a lot more sense.

draw_down 3y ago
[dead]

croisillon 3y ago

fyi you are shadowbanned, write hn an email to clear that up

brightball 3y ago

“Every” is a bit extreme but I’ve been a believer in Graceful Degradation for years. This is where jQuery excelled.

blackoil 3y ago

A ridiculously small but very vocal minority which is active on forums like HN.

ryanbrunner 3y ago

I tend to make all my pages function without Javascript even if I don't expect my users to turn off Javascript. It makes things easier to cover with automated tests if I can just exercise my backend servers with scripts vs. a headless browser, and if something does go wrong with serving Javascript or something it's nice to know my site is functional. Generally speaking the experience will be horrible (what should be a modal or a partial page reload will be a full reload) but using the technologies I use it's not that hard and it makes my development experience easier while delivering some (rarely needed) benefits to end users, so it's an unqualified win for my particular use case.