2 ms·
It's not always the right tool but in more cases than modern devs believe, it is. I've built several web applications recently that don't use any modern JavaSc
by jmathai 2y ago
It's not always the right tool but in more cases than modern devs believe, it is.
I've built several web applications recently that don't use any modern JavaScript framework. You'd be surprised how quickly a page can fully reload and equally surprised at how okay of a UX it is to not always persist state.
Here's an example video of an app that does a mix of "state persistence" and "good ol' reload the page" approaches. https://withlattice.com/documentation#nav-create-application https://withlattice.com/documentation#nav-create-application
1) Chat interface maintains state (but uses minimal JavaScript)
2) Application status requires a reload
Is this the absolute best UX? Possibly not, but users haven't said anything about it and it's such little code with almost zero dependencies.
- edoceo 2y agoNobody complaining isn't necessarily a "good thing". Absence of evidence and all that. I've found that it's only like 1/1000 that will. And this thread (few days ago) about why it's hard to buy nice things touches it https://news.ycombinator.com/item?id=42430450 https://news.ycombinator.com/item?id=42430450 Many (most?) don't raise issues because they've been conditioned that things won't get fixed. I'm with you that overdone JS isn't necessary; and we should also consider user-silence to issues to bloat, slowness and jank.
- jmathai 2y agoI agree with all of that. Perhaps what I meant to say was that these weren't the things users were complaining about. I love a beautiful UI and experience. Listen to users and prioritize what helps them.