“Why does Chrome not have a good tab management system built in?”
plus.google.com
plus.google.com
I know those things because I frequently have >200 tabs open, and have done so for many years. But I'm not surprised that it would be considered too niche to fix, because the reactions of most people (among a fairly tech-savvy sample of people looking at my web browser) go to the point of making comments about their surprise at how many tabs are open on my screen. It just isn't very common behaviour.
During the 'graphical glitch' era, I was an intern on the WebKit team at Google and asked about the bug, and some people knowingly chuckled and said, "yeah, that isn't something that's going to be fixed soon." I imagine it was also a tough bug.
Anyway, it would still be cool to support better tab features.
"Have you actually seen how people use web browsers? Honestly it's kind of horrifying. It's not unusual for people to have 100+ tabs open across several different browser windows in a session that's been running continuously since sometime in the late 90s."
I was one of those 1k+ tabs people until recently, when I just admitted I'm not going back to read any of this stuff. Considering Chrome team has finite resources I'm glad they spend it on use cases resolving around actually browsing things over just keeping them unread forever.
http://i.imgur.com/FBXmBqh.png
Then i have a second window which i use for work. That generally has a few work-specific tabs (work email, time tracking, trello, etc...) which are always pinned, plus a few "general work" tabs which i'm using.
Then i like to open a new window for each project i'm working on. So i've got one right now working on integrating node.js with our 80's language. That window has about 15 tabs from the node manual as well as the 80's language manual and some stuff about dlls in windows.
Then i have a window for my personal project i'm currently working on. It has the github repo, travis.ci, coveralls, and sauce-labs pinned, as well as the handful of tabs that i'm currently using in that project (research, test tabs, various other crap).
It totals to about 4 windows, and about 100-200 tabs total depending on how busy i am any given day.
I don't bookmark or close them because i don't have to, and while some of the pinned tabs are important, many of them are just where i left off and aren't really bookmark-worthy.
I think that's probably what mscrivo was curious about.
Every "tangent" i need to explore, or every other level i need to dive into opens another tab, and by hitting CTRL+W i can pop them off when i'm done and go back to where i split.
So i have had times where there are 50+ tabs in a window, but generally that's the exception not the rule for me, but i can easily understand how people get there normally.
One of my friends uses "google searches" as a form of note taking. It's "backed up" to his history, 90% of them end up as a search at one point anyway, and it's easy to open one and type it in without any extra steps or much thought at all.
I often end up with many (read, ~100? Varies widely.) tabs open.
I work like a priority queue. When I'm reading something, and see something interesting as a link, I open it in a new background tab and keep reading the current thing. Then go to the most interesting/relevant/time-sensitive tab I have open and read that. Repeat. ( while not que.isEmpty(): que.pushAll(que.popBest().getChildren()) ) This adds up quickly.
For example, with HN I tend to browse the entire front pages (active / standard) / my user threads before I actually start reading links / comment pages. And when I'm reading a comment page I tend to open comments to reply to in a new tab to get back to them later.
Ditto, if I'm coding something unfamiliar I often find myself looking up things recursively. Oh, here's two options to do thing A I need to do. Oh look, option A requires things B and C. Oh look, B requires D. This is sounding too complex, close tabs for things A/B/C and try option 2 instead. Etc.
Realistically, I only need at max two or three tabs actually loaded at once most of the time - but at the same time I want things to be loaded before I get to them, and I do not want to lose data from unloading pages. Lazarus helps, but there are pages that still lose data on reloads.
With tree-style tabs (Fireox), it's possible to see the relationships between tabs, with parents and stuff, so you can close an entire subtree trivially. For Chrome, that's not possible.
Even with Tab Outliner (which I've got), the disconnect between the T.O. window and the current window is utterly lost.
Also, for memory management, I cannot simply "unload" the current tab from within Chrome (though apparently with extensions that's possible). I do browse with the Task Manager open and routinely kill off windows to free memory. But that's also less than optimal.
Lots of make-work for shit my computer should be able to keep track of and handle for me.
There's a huge gaping hole between tabs and bookmarks which needs filling. Essentially a "stuff to be read" queue, though with relations back to the parent document / page.
That backlink is where tree-style tab managers win. Firefox also delays page load to when you actually navigate to the fucking page, which Chrome utterly fucks up.
With these two methods I frequently hover around ~20 tabs open and I usaully dump to either method when I cross the close-button threshold (tabophiliacs will know what I mean).
Recently I've been trying to force myself to use Firefox to use their tab groups feature and I think I really like it especially for organizing tabs needed for projects. Makes it easy to just click the tab group button and select which project I'm working on and immediately have all the tabs I need.
That's a completely emotional response. "It makes the tab bar completely unusable" -- maybe the problem is with the tab bar, not the user. What if browsers were designed for the lots-of-tabs use case? Perhaps if effort was put into it, we could come up with some good solutions. I would bet that there's a not-insignificant number of users who have heaps of tabs open.
My browser bookmarks just fine. Why do I need all these pages currently loaded into memory?
"problem exists between chair and keyboard"
If people want thousands of tabs then let's help them do that instead of shaming them.
I suspect a lot more users would use a lot more tabs if it were actually convenient to do so.
They've completely disregarded the possibility that the lack of effective tab management is limiting most users to use only a tiny number of tabs.
Tree Style Tabs for Firefox has been an integral part of my browsing experience ever since I discovered it: http://i.imgur.com/PnpZwos.png
I just wish some browser vendor would release an official vertical tabs solution that had a more seamless implementation of autohide/autoexpand (for non-maximized windows where horizontal space is at a premium).
Hold right click and scroll your mouse wheel down (you have to tweak a setting to have scrolling up also bring up the menu). Your tabs will appear where your cursor is as a drop down list, sort of like a context menu.
Combined with tab groups (ctrl+shift+e, or make another mouse gesture) and I can sort my tabs into categories and quickly switch between my tabs by either switching tab groups or using my mouse wheel, no matter where my cursor is.
So much time saved from not having to go to the top/side of my browser to switch tabs. :)
E:
The setting is under "Advanced" -> "Wheel Gestures" and the action is "[Popup] List all tabs"
Unfortunately, they started from stratch with Chromium-Opera, and even after more than 10 versions it still lacks most of the great features of Opera.
Day to day, I use both Firefox with Tree Style Tab, and Chromium with Tabs Outliner. This isn't perfect: Firefox still takes a minute to load the session with 700+ tabs, and Tabs Outliner feels kind of a hack and isn't really integrated.
Out in the wild though, it's something like, 95% of people never have more than 10 tabs open and 99% of people never have more than 20 tabs open. Don't quote me on the exact figures but those are in the ballpark of correct. It's hard to justify building a feature set for less than 1% of your users.
Besides that with the # of people using browsers a tiny minority can actually still be a huge # of users.
Slightly annoying it is per window though. I sort of expected the next window I opened to be able to 'boot' up an existing group. This seems to be just tab grouping rather than projects in any meaningful sense. They are only in session data and they don't sync.
Turned out I didn't, and Safari has lots of great features that are well thought through.
I still use Chrome for web dev, but it only runs a single tab with the web app I'm working on.
Try new things! :)
Now, if only they could fix bugs hanging around for more than 6 years, it would be cool too. ie: https://bugzilla.mozilla.org/show_bug.cgi?id=488725
In my opinion, managing tabs as a tree allows greater flexibility and enables one to see the "history" behind tabs (which tab opened which other tab).
- How would a user quickly set the category on a tab?
- I would presume that a user would only want to categorize things once the browser becomes unwieldy. How could it be done in bulk?
- Where would the UI elements for this go? Considering that Chrome strives to be minimalistic.
- How would the categories be communicated to the user?
- I should be able to tell Chrome "Hi, [... snip ...]" How?
I'm fairly certain that this idea has been mulled over multiple times, even by Google. The problem isn't having the idea in the first place, it's the implementation. I think that if someone wanted Google to "steal" this, they would need to approach them with viable mockups demonstrating an elegant solution that fits in with the spirit of Chrome.
Allowed you to have as many sessions as you wanted, though much of the time, I would end up realizing most of those tabs weren't that important and just delete the session later.
If you are on a Mac you can go a step further and create different desktops for different projects, the only draw back is if you accidentally Cmd + Q an app that is open on multiple desktops.
When the Chrome Sidebar API[2] is implemented, I'm sure it will only get better, as the need for an extra window should no longer be necessary.
Here's a video overview of its features: https://www.youtube.com/watch?v=OqjcrfKjobY
* I haven't reached the maximum yet...
[1]: https://chrome.google.com/webstore/detail/tabs-outliner/eggk...
[2]: https://code.google.com/p/chromium/issues/detail?id=51084
IMHO you always come across more tabs than you ever have a chance to read. And you'll always get back to them again when you actually need them via Google search.
I would love a tab sidebar. This might make Firefox worth checking out.
It also is utter pants when used with a focus-follows-mouse windowmanager policy.
Solving this with an extension seems suboptimal when Google may already have an internal unreleased project that does what I want.
If OneTab (or Spaces, another similar extension) could sync across my computers, this would probably be 90% of what I requested.
To a degree I can solve that with different browsers or profiles, but when clicking a link on irc or in a mail or twitter it always opens in the default browser.
My main gripe there's no way to have real context switches there, then again maybe I would just have to find a way to send a certain tab to a certain browser instance with a keyboard shortcut...
Manage Tabs - https://chrome.google.com/webstore/detail/manage-tabs/kijdih...
But then people don't want to use a tiling windows management because it's too hard to learn...
Bookmarks are both too painful to manage or navigate (and despite both limitations, I use them extensively). Tabs address the situation of "I want to read this but not right now". Chrome's implementation makes managing, prioritizing, and relating tabs all but impossible.
The larger problem is that the entire browser paradigm is approaching its end-of-life date, and what is now "the browser" almost certainly wants to be four distinct classes of application:
* Reader: a document-oriented applicaton with commenting, bookmarking, newsfeed, bibliographic management, annotation, and commenting capabilities. A bit lof the love-child of the original Web browser model, eBook reader, RSS/Atom feed, Readability or similar "simplified Web" presentation tool, Usenet newsreader, and tools such as Zotero or Calibre. Actually, Zotero, Calibre, or an eBook reader might well assume this role.
* A generalized application platform. A cross between current "full-featured" browsers and mobile development environments. Likely based on the concept of downloading the App framework only when it updates, containing it within a sandboxed runtime, and interacting with cloud-based services as needed.
* A dedicated commerce platform. Firewalled from other uses, increasing both privacy and security, with purchase, order-fulfillment, and related functions offered securely. Possibly growing out of a dedicated commerce app, e.g., Amazon or iTunes.
* A dedicated media player. Rather than having dozens of videos and audio players scattered among browser tabs, a single application which can enqueue, play, and/or schedule playback. VLC is closest to this, and has many of the features I'd like, though none of the stability. youtube-dl, local filesystem storage, and mplayer are my usual solution these days.
https://www.reddit.com/r/dredmorbius/comments/256lxu/tabbed_...
Yes, I've heard the "but heavy tab users are a minority case".
Answering that:
1. They're power users. Power users are a minority case. They're also a strong influencer community, and they lead migrations. Google Chrome (as with much else at Google) is no longer attractive, it's simply not sufficiently repulsive. But it's a tool people are using because they perceive either alternatives or siwtching costs as insufficiently better. That can change rapidly.
2. If you make something sufficiently painful, well, NO SHIT. People will tend to avoid it if they can. Power user's can't avoid it, and will find alternatives, eventually.
It's not even a matter of "oh, I'll get around to reading that stuff. It's that the state of tab management, on top of memory issues with Chrome, is so fucking abysmal that I cannot sort out what the fuck is in tabs, or how they're related.
Eventually the session crashes and I start over, but there's always painful state loss involved.
Why do I still use Chrome? Stylebot + Developer Tools. The state of Web design is so fucking abysmal that I've got 1700+ local stylesheets applied to various websites that I'd have to port and load somehow in Stylish on Firefox. And ... as annoying as other bits of Chrome are, the Developer Tools are decent, so fixing fucked-up Web design's a tad easier. And given the option of wanting to stab my eyes out staring at crap pages or dealing with Chrome's utterly fucked up memory and tab management ... tabs win, just barely.
But love Chrome? Who the fuck are you kidding?