@jer_ It's so simple, too, and I use this button *a lot*
I also am, well, kind of vehemently opposed to excessive js on pages.
And a big reason for this is that we can ship sites without a dedicated backend—which we would need to render your sites for you when you disable JS. A requirement for a backends just to render templates would be a very high obstacle for many applications and developers, in complexity, time, cost, and electricity. It simply wouldn’t make sense.
@jer_ But I do appreciate the point you are making and I will rework my sites that would show a blank screen to instead render a nice explanation of what the goal of the app is, as an invitation to enable JS.
You’re also right that many devs will host their client-side-only sites on free static providers like GitHub Pages which are built on top of CDNs and cloud storage providers that are storing and mining visitor logs. There’s some room for shenanigans. There’s also a lot of room for privacy: I can guarantee visitors to my static site that nobody will see the data they enter into it because no packet ever leaves. And static sites offer the ultimate immunity to vendor lock-in: literally anything can serve dead bytes on disk.
- websites-as-books eg. https://ageofdatini.info/
- Displays of data by public institutions eg. weather reports, bus schedule
- News sites, job posting sites
- Collections of photos with metadata
- Video hosting sites
- Mail clients
@bookandswordblog @jer_ thanks for bearing with my incomplete walls of text! Read-only databases are topologically equivalent to static files (see the fantastic https://phiresky.github.io/blog/2021/hosting-sqlite-databases-on-github-pages/).
I still don't see any justification for most types of site being unable to show their basic factual content without enabling active scripts.
@22 @bookandswordblog all of this that you're describing, though, is foisting off the developer's inexperience on the user. That's a bad web app. If there are elements of basic usability that don't have to be client-side that are exclusively client-side, that's bad implementation.
I'm not talking about elements that require client-side work, but websites who just show broken images without js (or nothing at all) are bad.
@jer_ hmmm. Again many thanks for spending time reading my scattered thoughts and thinking about and writing a reply—I am supremely grateful for your thoughtfulness.
I don’t want to try and change your mind—I personally do respect the no-JS folks and as a courtesy to them I will spell out why they should turn on JS to appreciate a site I made in the <noscript> tag. I also love exporting websites with LaTeX equations and diagrams and source code snippets fully baked to HTML and SVG, no JS needed, to enjoy that sweet static files hosting. And finally a no-JS browser is of course in my toolkit for surviving the web (along with ad blockers and DNS blockers and proxies and VPNs and virtual machines).
But I personally can totally see why something that *could* have been a static site like Imgur or Twitter or Medium still decided to do rendering and interaction to JS. To me it’s a reasonable choice and I disagree with calling them “broken”.
@22 @jer_ @nolan I brought it up before, but what does "web app" mean to you? To me it makes no sense to call most types of websites an app, in the way a browser mail client or GIS based map maker is an app. As I and Jer said, our main objection is not to "programs in a browser" requiring active scripts but simple displays of information requiring them.
If its all one page which loads and reloads, that suggests a site is more a web app than a web page.
@bookandswordblog (dropping others) right I can see how that can be confusing. Notionally I think of a web _app_ as something that needs interactive programming (mail client, GIS, game), but that’s too innocent because it might lead you to think think bus timetables 🚌 or prose essays don’t need interactivity. However that’s only true from the _consumer_ point of view. In in our capitalistic world, the _publisher_ of such content might be very interested in knowing exactly which parts of the page you look at for how long (IntersectionObserver does this https://developer.mozilla.org/en-US/docs/Web/API/Intersection_Observer_API), what you selected or clicked or copied, and of course when to insert an ad. Thus even these “informational displays” wind up becoming web apps 🙄.
(Despite my eye roll I don’t think it’s useful to have an automatic revulsion for such “tracking”. I’ve worked with authors of complex technical training, like that MDN link above, and these content creators are extremely interested in knowing what pages/sections were useful, how long readers dwelled on each section further broken down into how frequent a visitor they were, etc.)
@22 as someone who has been running his own sites since 2013, making money from them since 2018, and created his own static site generator in 2021, I don't need those kinds of interactivity. I track traffic by page visits. The bus system makes its money selling tickets not PII, and advertising which is targeted at page load has been an unmitigated disaster for advertisers, publishers, and the public (its great for fraudsters tho) https://adcontrarian.blogspot.com/2021/01/the-inescapable-logic-of-ad-fraud.html?m=1
The creator isn't the arbiter of the effectiveness of the design, the user is. When we, as an industry, add bloat and complexity for reasons that don't benefit the user in any meaningful way (and in many ways injure user experience) then we're building bad software.
@jer_ @22 regarding user experience, one important reason to block scripts is to remove nagging popups asking visitors to sign in, sign up to the mailing list (which they are already on!), disable their ad blocker, fill out a poll, etc.
NoScript and UBlock Origin would not be so popular if they were just used by privacy geeks.
Its not just about privacy or saving bandwidth but about seeing the actual content without all the cruft laid around it.
@bookandswordblog @jer_ your unexpectedly generous and patient explanations convinced me it’s time to properly learn server-side rendering which is why I’m neck-deep in the Next.js documentation at 2am 😆
It turns out my intuition about the difficulty of converting a traditional React or Vue single-page app (SPA) into something more static when you also have a backend handy is at least a couple of years too old. I personally didn’t take tools like Next or Gatsby seriously because they’re outside the orbit of the core language and framework teams, but with the newfound energy to figure it out thanks to your posts, I see that these are definitely worth using and the direction the industry is heading in.
Well done to both of you. Someone (me) was wrong on the internet and you fixed it 😁
@jer_ also, I am impressed by all the things you can do with HTML and CSS these days! I came back to creating my static site after ten years in grad school.
If you are building a website not a web app, HTML and CSS will take you far and are more stable than third-party active scripts.
suggestion of mild violence
The Wandering Shop is a Mastodon instance initially geared for the science fiction and fantasy community but open to anyone. We want our 'local' timeline to have the feel of a coffee shop at a good convention: tables full of friendly conversation on a wide variety of topics. We welcome everyone who wants to participate, so long as you're willing to abide by our code of conduct.