A different kind of tab-based filesystem that would be nice:
Expose all the resources used in each tab in a virtual filesystem (JS, CSS, images, HTML, fonts, etc) in a folder for each tab. Basically Chrome Developer Tool's Sources tab but as files and folders on your computer.
This would be great for scraping with headless browsers. It'd let you use shell scripts or your favorite programming language's filesystem library to read/copy assets, rather than writing code with Puppeteer to copy files/data.
It would have to copy from Chrome directly though, rather than re-fetch the content
This sounds actually very similar to what I am building, if you ignore the Chrome part [1] :)
The general idea is to have more persistent caching locally, so that peer offloading (and persistence of offline content) can be guaranteed.
Since yesterday the cache supports multiple versions of each file (with a timestamp), and it will get a UI that allows to navigate back in time for each URL.
I think they were thinking more along the lines of a live system. Where you could change the settings of the page in real time using the filesystem interface.
Expose all the resources used in each tab in a virtual filesystem (JS, CSS, images, HTML, fonts, etc) in a folder for each tab. Basically Chrome Developer Tool's Sources tab but as files and folders on your computer.
This would be great for scraping with headless browsers. It'd let you use shell scripts or your favorite programming language's filesystem library to read/copy assets, rather than writing code with Puppeteer to copy files/data.
It would have to copy from Chrome directly though, rather than re-fetch the content