51–60 of 129 posts
Earlier quoted context omitted.
Literally modern frontend frameworks that don't want to do SSR. Is it that surprising?
The only useful content on the page was not only static text, but static plain text. If the modern frontend framework can't display that without JS, then I think it's fair to call it a shitty frontend framework.
Earlier quoted context omitted.
JavaScript poses a large security and privacy risk. Think browser fingerprinting, XSS, JS-based analytics, poor or missing CSP + hijacked npm modules, etc. I generally keep JS disabled as much as possible.
You can perform analytics almost as well from just the HTTP headers, you don’t need JS at all for fingerprinting, and hijacked NPM modules are probably still present even if there is no JS pushed into the browser.
The OMG JavaScript, parade of articles is tiresome / endless and IMO is trending towards the absurd, and it kinda irks me. I could really go without ever hearing someone bemoan how they rewrote an internal react site in 10 seconds with two lines of JavaScript, or whatever old wives tale they've got going on. If it was that easy then maybe it also wasn't the end times? Yeah there's a lot of pages that maybe could get…
There is almost never any new insight, and you could copy+paste comments from one to the next and not know the difference.
We get it, Javascript is the worst and everything should run perfectly without it - at least to the vocal minority of users who actually care (which is basically just HN's demographic).
Earlier quoted context omitted.
What percentage of city bus riders or public restaurant visitors do you think use the wheelchair ramp?
What percentage of people in wheelchairs are able to walk but choose not to?
Half the pages I land on now say "you need JS to view this site", and that's totally their decision! I close the tab and do something else: they get to use JavaScript, I save a bunch of time and procrastinate less... win-win!
Earlier quoted context omitted.
That's great and it's your choice to disable it but his point was don't expect developers that rely on JavaScript to power modern web experiences to develop their site to fit your strict requirements. JS does way more then just fingerprint users and open up security vulnerabilities. You're in a minority that's asking for fall-backs in a world that's so far removed from simple fixes.
> power modern web experiences So they're going to expect me to leave a major malware and privacy-invasion vector open so they can indulge in creating their 'web experiences'. Nope. This sounds like kids playing around, not professionals working.
a quick way to check is to use elinks for instance
The OMG JavaScript, parade of articles is tiresome / endless and IMO is trending towards the absurd, and it kinda irks me. I could really go without ever hearing someone bemoan how they rewrote an internal react site in 10 seconds with two lines of JavaScript, or whatever old wives tale they've got going on. If it was that easy then maybe it also wasn't the end times? Yeah there's a lot of pages that maybe could get…
The problem is that browsers are running apps when most users just want to read relatively static content. Our ever decreasing, day-one battery lives and swelling landfills are clear evidence this isn't sustainable.
The OMG JavaScript, parade of articles is tiresome / endless and IMO is trending towards the absurd, and it kinda irks me. I could really go without ever hearing someone bemoan how they rewrote an internal react site in 10 seconds with two lines of JavaScript, or whatever old wives tale they've got going on. If it was that easy then maybe it also wasn't the end times? Yeah there's a lot of pages that maybe could get…
> The browser now effectively runs apps, so it's not just going to read HTML The problem is that browsers are running apps when most users just want to read relatively static content. Our ever decreasing, day-one battery lives and swelling landfills are clear evidence this isn't sustainable.
Their eyes read, but they still interact as well.
Earlier quoted context omitted.
> power modern web experiences So they're going to expect me to leave a major malware and privacy-invasion vector open so they can indulge in creating their 'web experiences'. Nope. This sounds like kids playing around, not professionals working.
Ahahaha come on my guy, effective people get to where they are because they can make good risk/reward assessments. Turning off javascript hasn't been worth the opportunity cost to a "real professional" for decades.
Indeed, and I made mine. No ads, not tracking, no risk of malware, no need for virus scanner, high speed page loading (ahem, when it works). Worth it? For me, sure! Peace of mind means a lot to me.
What's so hard about making web pages that don't use unnecessary tech?