3 ms·
Back in the ancient days of the web, browsers allowed you to set resource limits (ram, cache, etc) to prevent websites from hogging the limited resources of you
by alyandon 8mo ago
Back in the ancient days of the web, browsers allowed you to set resource limits (ram, cache, etc) to prevent websites from hogging the limited resources of your desktop system.
It's really a shame that all major browsers have since decided that you as a user should have almost no control over how much ram and storage any arbitrary website can consume now.
- deleted 8mo ago[deleted]
- dijit 8mo agoGoes with the territory of allowing remote code execution arbitrarily and all the time otherwise you won't be able to.. * checks notes * read text on the internet.
- wiseowise 8mo ago> read text on the internet. B—b-it 4K scaling! Reactive design (to read text)! Emojis, reactions, badges! Memes and gifs!
- mghackerlady 8mo agoAll of which can be done with HTML, CSS, or UTF-8
- arantius 8mo agoThis is a fantastic claim. I've been making web pages since the '90s and using web browsers just as long, and I can't think of a single instance of this. Perhaps it existed and I never knew about it? Can you provide some evidence for where and when this was the case?
- alyandon 7mo agoOld versions of Netscape Navigator had settings where you could tweak that kind of stuff - I don't recall if IE3/4 did or not. Given the web of the 90s didn't include tons of overly complex javascript most of the settings were targeted at how much ram/disk was used for caching website assets IIRC. It's the principle of the thing though - we should have the ability to set resource allocation limits instead of potentially handing our entire computer's resources to a random website just because we clicked on a URL.