191–200 of 283 posts
1. Just. Fucking. Unload. The. Tab. Already. I keep tabs around for context and reference. Lots of them. [1] 2. Preserve. User. State. I don't want the page to reload. I want what had been there to be restored. Page position, content, any inputs or adjustments I'd made. Not updated data, but previous state. 3. Do. Not. Lose. My. Shit. I can accomplish this far better myself than you will ever have need to do. 4. Any…
You have 1,530 tabs open?!
Earlier quoted context omitted.
>Turning off Javascript won't suddenly make 900+ tabs easy to manage. I'm fine with searching. I want to have searchable fulltext in those 900+ tabs. Just for a back of the napkin calculation, I took the plain text from this comments page and saved it, and it came to 52kb. My PC has 64Gb RAM. So even without any form of compression or indexing, I should be able to hold searchable fulltext of over a million tabs in RA…
I’m not sure if I’m missing something, but nvme drives are pretty rapidly approaching ram in terms of bandwidth, so it’s possibly sane to just offload tabs to ‘slow memory’ too.
Earlier quoted context omitted.
Why not cache the HTML/CSS instead of using a screenshot? I'm no expert on web/browser development, so I don't know the difficulty or feasibility in caching just the visible bits leaving a static HTML/CSS snapshot minus any javascript seems, but it seems more ideal IMO since you'd still be able to click links. Just a thought
Good Q! It is something we are looking at/trying. It's a bit more complex as you have to have a pool of suspended renderers to swap the html into as the user switches tabs (the HTML still needs to be properly sandboxed). Then you include static asset loads, etc it becomes less 'instant'.
Look forward to trying this out when it becomes available for an OS I use.
Earlier quoted context omitted.
I was surprised recently to learn about the back/forward cache (bfcache) [1], a common browser optimization that sort of does what you're describing but stores a more complete snapshot of the page, including the JS heap. I'm not sure if it's used in this new FF feature (the article doesn't give details about the mechanism of unloading). However the bfcache unsurprisingly causes edge cases in JS-heavy pages/SPAs, and…
Only recently when I flew backwards through about 50 history steps (entirely different webpages) on my phone did I think more deeply about how impressive it was that it was so seamless.
1. Just. Fucking. Unload. The. Tab. Already. I keep tabs around for context and reference. Lots of them. [1] 2. Preserve. User. State. I don't want the page to reload. I want what had been there to be restored. Page position, content, any inputs or adjustments I'd made. Not updated data, but previous state. 3. Do. Not. Lose. My. Shit. I can accomplish this far better myself than you will ever have need to do. 4. Any…
Entitled is the word.
Earlier quoted context omitted.
This is not an angle I’ve heard before - how does an SPA save money?
Offload computations and rendering to the client
Earlier quoted context omitted.
SPAs can easily handle routing via the history API, the problem is that companies haven’t migrated correctly.
It’s usually crappy though, like the URL and the history don’t accurate recreate the state of the app on refresh at all, or the history gets so clogged with every mutation of app state that the back button is effectively useless.
Earlier quoted context omitted.
This is not an angle I’ve heard before - how does an SPA save money?
It’s cheaper to build single page apps using web developers than to build and maintain multiple platform-specific native apps.
Could you provide examples (not exceptions) maybe to support your PoV?