You must log in or register to comment.
- Piatro@programming.devEnglish6 months
Got to disagree there. Websites should work without js. Sure it shouldn’t have fancy animations or whatever but I should be able to read it.
- Denys Nykula@piefed.socialEnglish6 months
JavaScript has been my favorite language for a decade. Still, I try to make websites server-rendered so that they can be read if my code fails to load or execute. For example, there are power outages in Ukrainian cities for most of the day because of the war. When there’s no power, there’s still 4G for a while but it switches to economic mode and slows down to a crawl. The websites of the monopolist energy company require a lot of JavaScript. It often fails to load for me during the outage. It’s also not keyboard-accessible because of how its JS is implemented (I won’t image I’d do better, they have a team while I’m a solo programmer, but I try and they don’t). For me to see when there will be electricity at what place and plan where to go study and work, I have to rent a VPS, scrape their website and show me a static table that doesn’t require JS to load. Some code to see what I mean: https://codeberg.org/nykula/powerup
- 6 months
JavaScript was my first language because my initials are JS. After spending some time on programming.dev and seeing how many people bitch about JavaScript, I wrote a Python templating engine to convert Markdown into static HTML with CSS. I have like 10 lines of JavaScript that pre-populates a selector based on the URI’s query string, but that’s it. I got a perfect score on my Lighthouse report (and learns it gives you confetti when you do).
It took some creative problem solving, but I discovered that I didn’t need like 99% of the JavaScript or PHP that I was using. What I needed was mostly to get good at CSS.
- 6 months
So if for any chance you can’t use JS (outdated browser, outdated system, text-based browser, JS disabled by an admin, JS won’t load, assistive technology) then… it’s your fault?
- 6 months
- outdated browser - your fault, and a foolish thing to use considering the modern, online threat landscape
- outdated system - your fault, and like above you probably shouldn’t connect to the internet with that thing
- text-based browser - your fault, and it shouldn’t surprise anyone that websites break when you use a browser that misses major functionality
- JS disabled by an admin - your admin’s fault. Go complain to them, not to anyone else
- JS won’t load - depends on reason for why JS fails to load
- assistive technology - depends on the reason; your assistive software may be broken or misconfigured, or the website fails to follow best practice
- 6 months
You missed the point completely, though - you should not expect every user to have a shiny updated browser in a shiny new machine using your website, and blaming them if they don’t.
If you want your website being able to be used by most of users, you better cover all use cases. That includes providing non-js fallbacks. Not doing that and blaming the users instead is just ridiculous.