Earlier quoted context omitted.
Can you seriously not think of a single use case for SPAs?
Aside from cost-savings for the business I can’t really think of one.
This is not an angle I’ve heard before - how does an SPA save money?
Tab Unloading in Firefox 93
181–190 of 283 posts
Re: Tab Unloading in Firefox 93
#182Earlier quoted context omitted.
I'm not sure I follow. Either that or I'm not sure you understand what I'm trying to say. Turning off Javascript won't suddenly make 900+ tabs easy to manage. The UX isn't designed for that volume of separate pages, the tabs are cumbersome to navigate and still just don't really lend themselves well to large sessions that span multiple topics. I'd believe the same thing even if Javascript had never been invented, tab…
>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.
Re: Tab Unloading in Firefox 93
#183Earlier quoted context omitted.
Can you seriously not think of a single use case for SPAs?
Single-page apps are forgivable for media oriented sites, so the video/music can keep playing as you navigate the site. in the past this was done with pop-up players and was generally messier, so I like SPAs for this. Literally every other type of website on the planet should use traditional loading pages.
SPAs can easily handle routing via the history API, the problem is that companies haven’t migrated correctly.
Re: Tab Unloading in Firefox 93
#184> As long as there is still swap AND physical memory available, there is no problem. If we run out of physical memory and there is swap, performance will crater due to paging, but we won’t crash.
That's a disheartening stance to hear. The browser should be actively evicting work before I start swapping if it's using more than some small percentage of overall RSS. If my IDE decides it needs more RAM for code completion, the browser should play nice rather than slowing my machine to a crawl.
Re: Tab Unloading in Firefox 93
#185This has existed for two years now (option browser.tabs.unloadOnlyOnLowMemory) but someone had to manually enabled it.
Re: Tab Unloading in Firefox 93
#1861. 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?!
Re: Tab Unloading in Firefox 93
#187Earlier quoted context omitted.
Aside from cost-savings for the business I can’t really think of one.
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.
Re: Tab Unloading in Firefox 93
#188Earlier quoted context omitted.
Single-page apps are forgivable for media oriented sites, so the video/music can keep playing as you navigate the site. in the past this was done with pop-up players and was generally messier, so I like SPAs for this. Literally every other type of website on the planet should use traditional loading pages.
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.
Re: Tab Unloading in Firefox 93
#1891. 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…
I'm being using Total Suspender. it's a complement that auto suspend unused tabs, using the tab discard API described on the article.
I don't loose anything. It preserves the state. The usage of ram it's fantastic. And I'm only have around 40 tabs open any time.
This new native auto unload, don't loses anything and preserves the state. it uses the same API!
Re: Tab Unloading in Firefox 93
#190What I want implemented.. Chrome/Firefox whatever... is that instead of unloading and reloading when I go back to the tab I want it to export basically an HTML file and when I click back to that tab, I want it to reload the HTML file instead with some notification/marker that it is a "cached" version. There are times where I'll leave a tab in the background that I don't want refreshed but when it gets unloaded, poof,…
Firefox dont loses state or information when unloads a tab.