My issue with modern frameworks is that they seem to assume that you would only ever use them to write a single-page web app that would be unreadable but for enabling JavaScript. I don't think this is the web we should want.

Vue is (as far as I know) the exception that proves the rule. It's the only one, apart from older JS technologies like JQuery, that accepts that you might only want to use it to augment an already-functioning website.

Follow

We should want our web pages to be human readable without *any* JS. calls web pages that operate this way "curlable," and I think it's a great goal for a couple of reasons.

indieweb.org/curlable

First, it gives folks the option of enabling or disabling JS entirely on your web page. That may seem utterly unimportant to most people, but to some it's a deal-breaker.

Perhaps more importantly, it allows your web page to be read with tools other than a fully-featured web browser. In other words, increased accessibility. One upshot of this is that, for instance, archive.org can crawl and archive your web pages (which seems like a good thing to me).

Anyway, my point is that I think JS-heavy web pages raise issues of accessibility that I don't see folks—particularly in the JS community—wrestling with nearly enough. But that's all just my opinion.

Sign in to participate in the conversation
Mastodon

A private Mastodon instance