Slashdot Mirror
Firefox Tab Candy Alpha
Nunavut writes in with a note from TechCrunch on Aza Raskin's latest Mozilla goodie, Tab Candy. "Be sure to watch the video for a full overview — from the looks of it, it seems as if Tab Candy is sort of like Apple's Expose feature mixed with their Spaces feature, both of which are baked into OS X. For those who don't use a Mac, basically these features allow you to zoom out and get a bird's-eye-view of all your windows (or tabs, in this case) that are open — and you can also arrange open windows (or again, tabs, in this case) in certain spaces so they're clumped together. This allows you to more easily find what you're looking for with so many tabs open." Here's Raskin's blog post, the download link, and the FAQ.
Am I the only one that opens up tabs to read the content and then closes the tab after doing so? I don't really see why someone would have like 20+ tabs constantly just sitting open.
The "Tree Style Tabs" add on is great for managing your browsing. It gives your tabs context, lets you collapse groups of tabs and move tabs from one group to another. That, and having the tabs vertically arranged lets you have far more on screen at once and make better use of a widescreen monitor. Solving many of the problems addressed by Tab Candy.
I'm really surprised more people don't use it. It's the one thing now preventing me from switching to Chrome.
"Did you exchange a walk on part in the war for a lead role in a cage?"
Let's see, I've got multiple workspaces, with multiple instances of firefox running, and each has one or more tab.
But something is missing. It's just not fine grained enough.
If only tabs could have tabs!
The example which is given in the video from TFA to try to demonstrate the need for this tab candy nonsense is how a clumsy user can fill a tab bar with countless unrelated tabs. Yet, from the example which was presented, there is absolutely no need for that sort of crap. Let me explain.
In the example the user starts off with a browser window which already has tons of tabs, which is already in itself a sign that the user doesn't know what he is doing. From there, a case is presented where the user suddenly feels the need to start a new search, which happens to be completely unrelated to anything that he was already doing. Well, in that scenario, the user could very well do the very same thing that any semi-rational user does when he finds himself on that very same situation: open a new browser window dedicated to that search and go crazy with the search results. There, fixed. There is no need for this tab candy crap, searches/online tasks are perfectly compartmentalized, the tab bar is clean and cluttered, the navigation to/from opened pages becomes simpler... Everyone wins.
Now, let's look at what this tab candy crap brings to the table. So a clueless user who is perfectly incapable of organizing his workflow finds himself with a single browser window with dozens of opened tabs. He suddenly feels the need to open another dozen tabs to perform a completely independent task. According to TFA, the solution to his problems comes in the form of this tab candy crap. Yet, the only thing that it is capable of doing is offering yet another needlessly cumbersome step to do nothing more than provide a different, resource-expensive way to present to the user the tabs which he has opened.
So, in other words, this tab candy crap is nothing more than a window manager built into a browser. I mean, manually group tabs? List the tab groups which are currently opened? Put some tabs on the foreground while putting others on the background? Present the user with small icons representing the opened tab? If you replace "tabs" with "windows" you are describing pretty much any window manager out there. So why exactly is it a good idea to build a window manager into a browser?
Slashdot, fix your code or at least hire someone who is competent at it to do it for you.