JavaScript is fickle. It can fail to load. It can be disabled. It can be blocked. It can fail to run. It probably is fine most of the time, but when it fails, everything tends to go bad. And having such a hard point of failure is not ideal.
This is a very important point:
It’s important not to try making the no-JS experience work like the full one. The interface has to be revisited. Some features might even have to be removed, or dramatically reduced in scope. That’s also okay. As long as the main features are there and things work nicely, it should be fine that the experience is not as polished.
@adactio Hello Jeremy! I was wondering if you could update my name in this entry of yours: adactio.com/links/16385. It’s the only one I could find with a Google search, but maybe you mentioned me elsewhere as well. I’d really appreciate if we could update it. ✨ Thank you! 🙏