This is a brilliant piece of work. As someone who has thousands of tabs open, I've always wanted to "close all tabs with a single command", or view all the open tabs and mass select them and close, for years. Otherwise, going through them one by one and deleting takes forever. Now somebody make a vim pluggin so I can delete tabs by visual selecting a bunch of them and typing "d".
TabFS: Mount your Browser Tabs as a Filesystem
201–210 of 242 posts
Re: TabFS: Mount your Browser Tabs as a Filesystem
#202Earlier quoted context omitted.
That's not a GNU/Linux issue, BSD's have KDE too. Also, back in the day you could compile and run KDE perfectly on Solaris and Irix. >or even Windows based systems, to develop software for GNU/Linux based cloud environments. I/O is still crappy and limited.
Ideas like /proc and ToolTalk come from Solaris, no need for KDE to get inspired. Irix had similar ideas as well. That is the thing, these UNIX workstations had a whole stack experience, not what Linux or BSD ever were or are.
Uh, Irix with 4DWM and limited DE's were not as powerful as a FreeBSD workstation with KDE3. Not even close.
People compiled JWM, IceWM and KDE on Irix and Sparc machines because 4DWM and CDE were horrendously limited and slow.
Also, Urxvt ran circles on dterm on cpu/memory usage. Much, much snapppier and faster.
Re: TabFS: Mount your Browser Tabs as a Filesystem
#203Wow, this is awesome! My OS is heavily scripted and keybound, thanks to 15 years of cumulative incremental fixes and a kick-ass WM. The one thing that's frustrated me is the relative black box that my browser represents, and writing a shim between my WM and browser tabs has been on my TODO list for a long, long time (through a couple of aborted attempts due to a combination of Chrome's at-the-time obsolete documentat…
I use qutebrowser in one-window-per-tab mode and EXWM[1] as my window manager (with ivy for switching buffers). It still needs some more integration but currently is my favorite solution to this problem. [1]: https://github.com/ch11ng/exwm
Have you noticed a significant difference in memory usage? qutebrowser turns into quite the memory hog over time. I have to periodically restart qutebrowser so my hundreds of tabs go into suspended mode. Even suspended tabs use a good chunk of memory.
Yes, I should be better at closing tabs.
Re: TabFS: Mount your Browser Tabs as a Filesystem
#204Wow, this is awesome! My OS is heavily scripted and keybound, thanks to 15 years of cumulative incremental fixes and a kick-ass WM. The one thing that's frustrated me is the relative black box that my browser represents, and writing a shim between my WM and browser tabs has been on my TODO list for a long, long time (through a couple of aborted attempts due to a combination of Chrome's at-the-time obsolete documentat…
I use qutebrowser in one-window-per-tab mode and EXWM[1] as my window manager (with ivy for switching buffers). It still needs some more integration but currently is my favorite solution to this problem. [1]: https://github.com/ch11ng/exwm
Re: TabFS: Mount your Browser Tabs as a Filesystem
#205Earlier quoted context omitted.
Ideas like /proc and ToolTalk come from Solaris, no need for KDE to get inspired. Irix had similar ideas as well. That is the thing, these UNIX workstations had a whole stack experience, not what Linux or BSD ever were or are.
>That is the thing, these UNIX workstations had a whole stack experience, not what Linux or BSD ever were or are. Uh, Irix with 4DWM and limited DE's were not as powerful as a FreeBSD workstation with KDE3. Not even close. People compiled JWM, IceWM and KDE on Irix and Sparc machines because 4DWM and CDE were horrendously limited and slow. Also, Urxvt ran circles on dterm on cpu/memory usage. Much, much snapppier and…
Re: TabFS: Mount your Browser Tabs as a Filesystem
#206Earlier quoted context omitted.
I don't think it was KDE 3 -> 4 transition that killed khtml. I was only around in the last year or two but KHTML [0] was mostly developed by a single volunteer on his spare time (Hi SadEagle in case you're reading this). There were occasional commits by other people but the majority of KHTML's development was done by him. You see, Konqueror as a web browser didn't even have a single full time developer. That was the…
That's fascinating, also that it was written by a single person. I remember how surprised I was when I discovered that Konqueror was at that point in time on par or better in terms of rendering quality compared to Mozilla and others. Also browser speed, memory usage etc. was just flawless. But yeah, IMHO one person projects are doomed to be abandoned unless the person is really dedicated to that project. (glibc maint…
Re: TabFS: Mount your Browser Tabs as a Filesystem
#207Earlier quoted context omitted.
If you are serious about spending 25k, please contact me, we are working on the Nyxt browser. Email us at hello@atlas.engineer
IMHO an extension for existing browsers seems like a better idea than creating a new browser. Why did you choose the latter approach?
Re: TabFS: Mount your Browser Tabs as a Filesystem
#208Earlier quoted context omitted.
> well-managed environment (ie one that has non-rudimentary window management and a browser/extension that handles idle tabs with negligible ongoing resource use). Can you elaborate on this? Which extensions are you talking about? I also rack up hundreds of tabs and my browser is often the main resource hog for me. I’ll often have to kill -9 it to force it to start with “oops we crashed, here are your previous tabs i…
I currently use the Great Suspender on Chrome, which will suspend a tab that's been open for a while. The suspended tab just shows a Great Suspender icon, so it takes up ~0 RAM. I've whitelisted certain domains and sites (eg Messenger apps). I know there are a ton of extensions aimed at this problem, including OneTab (which will collapse many tabs into a single page of links), but TGS works the best for my workflow.…
I could really use something like the Great Suspender. However, looking into it, I found quite a bit of controversy surrounding its new (since June) "maintainer". This issue sums it up well: "SECURITY: New maintainer is probably malicious"[1]
Here is the gist of it:
> Using the chrome web store version of this extension, without disabling tracking, will execute code from an untrusted third-party on your computer, with the power to modify any and all websites that you see.
So, installing from the Chrome Web Store is a complete no-go.
One can still install the extension from GitHub, but with Chrome constantly evolving and the now, unmaintained-on-GitHub extension having known issues with losing all your tabs (to which there are workarounds), I'm very wary of using this extension.
[1]: https://github.com/greatsuspender/thegreatsuspender/issues/1...
Re: TabFS: Mount your Browser Tabs as a Filesystem
#209Earlier quoted context omitted.
>thousands of tabs open yeah about that, are you sure they are open and not hibernated? Chrome had proactive-tab-freeze-and-discard , later renamed to proactive-tab-freeze and finally forced On in 80 with no option of turning it off. 'hibernated' tabs are merely a bookmark without loaded content. I dont think this extension would be able to work with non loaded tabs without forcing them all to load. 300 tabs is able…
Somehow, Chrome doesn't seem to actually do this despite claims to, which is why I use The Great Suspender (a Chrome extension that actually hibernates tabs).
Re: TabFS: Mount your Browser Tabs as a Filesystem
#210Earlier quoted context omitted.
> Like you I am an avaricious multi-tasker over extended periods of time and was heading towards the same state you appear to have reached. > I realised it was not optimal I will take a look, thank you! Would you mind briefly elaborating on what you found suboptimal about the workspace/window/tab hierarchy for organizing your tasks? So far it's working very well for me, and the low friction is a really important part…
My issues with tabs, even with extensions that organise them: * sheer mental challenge of quickly relocating related tabs and the context for why they were kept and relationships between them * inability to easily add WIP notes and commentary * difficulty of sharing tabs and context with others * possibility of losing them if power lost unexpectedly (during extended suspend for example) or accidentally close a single…
It's designed like a todo list which is a layer out to keep that context