Thank goodness you exist, the fingerprinters will be confused as to which one of the two of us went to their website!
replyHow? There are dozens of us! DOZENS!
replyHow would you count?
reply"you don't have to, they'll tell you."
reply(+1)
i'm right there with you!
replySingle page applications are one of the most anoying web patterns i know of. Please just let me have one page for each ting to do so i actually can bookmark it properly.
replyOnce backend and frontend became two separate teams frontend people didn't want to keep asking backend to make logic changes for state, so frontend took things into their own hands. The mistake was making it two separate teams.
replyThis is possible and, in my experience building them, the norm. SPAs have routers and update navigation state, including history for browser Back/Forward
replyYes true. But also way to often neglected.
replyIve made SPAs in Blazor that make it a point to update the URL whenever a "navigation" occurs. I also made it a point to ensure refreshing or loading the URL restored the state.
replyIt's a small problem compared to the ease of use for development you can gain via Blazor, so I don't see any reason not to solve it.
On the other hand, converting a SPA to a PWA is often a breeze
replyOne thing you notice running NoScript is how prevalent Google is.
replyEven if a site doesn’t monetize with Google Ads, there’s a decent chance it’s pulling a script from ajax.googleapis.com, and Google still knows that you visited the site from the Referer of the script download.
This is part of how I judge how well made or how shitty a website is. If it requires scripts from a dozen third parties, then it usually sucks and one can easily recognize when not much effort has been put into making it.
replyDoes HTMX work with NoScript? Doesn't it require JS?
replyNope, doesn't work. Doesn't stop you from making it a PWA, though.
replyoh my. Looks like NoScript is way better than what I've been using. Thanks!
reply