4 ms·
“Normal users” have JS enabled and don’t care how much JS you send them. They don’t even know what it is. I feel like if you’re targeting a no-JS crowd, that’s
by jen729w 3y ago
“Normal users” have JS enabled and don’t care how much JS you send them. They don’t even know what it is.
I feel like if you’re targeting a no-JS crowd, that’s a very specific crowd, i.e. this one.
- zelphirkalt 3y agoI would like to add: If the GP goes for any JS based solution, they should make sure to serve the JS themselves, and not outsource it to 3 CDNs. For us not liking JS too much people, the next best thing to no JS is little JS server by the website's server itself. Best with most of the website already rendering without JS, so that we see things when hitting the website and may consider it worth allowing its first party JS. Being able to see the website and get what it will use JS for goes a long way building trust.
- iamsaitam 3y agoDoes the no-js crowd also use aluminum foil hats?
- unshavedyak 3y agoI do plan on self-hosting all (the very select few i use) JS and CSS. It's part of the binary for dead simple self-hosting. I'm going to attempt to be very privacy friendly, as much as possible, which will be an interesting adventure because it's ActivityPub related. Regardless this is all just an exercise for me because, frankly, i hate most websites lol. The ones that look good also tend to be slow. The ones that are fast look like they're from 1990. There has to be a middleground, right? I love that feeling of visiting some (very few) sites and they load so fast you have to double-take. I want to be that site. I want accessibility to be forefront. etc We'll see how far i can get. I'm just a humble backend dev hah. But the site being 95% plain HTML is a good start, at the very least.
- jen729w 3y agoHere’s a comparison for you because I just did the same. Old site. - Built with Gatsby, hosted on Netlify. - Lots of client-side JS, but page loads are instantaneous because everything is prefetched and a page load is a client-side JS event not a server request. - https://v4-johnnydecimal.netlify.app/ https://v4-johnnydecimal.netlify.app/ New site. - Built with Astro, hosted on Netlify. - Zero client-side JS, but each page load is a good ol’ fashioned HTTP request to the server. - Pages are small. After caching my web fonts, each page is single-digit kilobytes. This is deliberate, I worked hard to achieve this. - It doesn’t feel as fast. Because it isn’t. Because it can’t possibly be. - https://johnnydecimal.com https://johnnydecimal.com