- cross-posted to:
- mildlyinfuriating@lemmy.world
- cross-posted to:
- mildlyinfuriating@lemmy.world
Long considered malicious website behavior (and defined as abusive by Google), back button hijack is starting to rear its ugly head again. The lower panel in the image is what tomshardware.com displays when the back button is selected. The enshittification continues.


Honestly though, as both a developer and a user SPAs could get fucked for all I care. I don’t think it’s a requirement of SPAs, but they seem to do so much unnecessary bullshit. So many bad development practices. I don’t hate the concept of SPAs, but it’s clearly just asking too much of the average contract developer.
As a developer as well, I agree that they can get fucked. Bloated crap that wastes bandwidth and ruins first-time-to-paint on mobile devices by necessitating downloading and initializing a multi-megabyte bundle of npm packages.
As a user of the internet, I need websites to work, however. I would have disabled JavaScript entirely by now if it weren’t for the fact that doing so renders what feels like half of the entire web unusable.