Slashdot Mirror


With Community Help, Chrome Could Support Side Tabs Extension

jones_supa writes The lack of a vertical tab strip (or "Tree Style Tab" as the Firefox extension is called) has been under a lot of discussion under Chrome/Chromium bug tracker. Some years ago, vertical tabs existed as an experimental feature enabled with a "secret" command line parameter, but that feature was eventually removed from the browser. Since then, Google has been rather quiet about whether such feature is still on the roadmap. Now, a Google engineer casts some light on the issue. He says that a tree-style interface for tabs would be overly complex as a native implementation, but Google would back the idea of improving the extensions interface to support a sidebar-like surface to render the tab UI on, if someone from the open source community would step forward to do the work to drive the feature to completion.

117 comments

  1. Google hates widescreens by greenwow · · Score: 0

    None of their products work well with them.

    1. Re:Google hates widescreens by Anonymous Coward · · Score: 0

      There's very limited vertical space on modern monitors so it makes no sense for them to be so adamant about taking vertical space. At least Microsoft allows you to move the taskbar to one side or the other.

    2. Re:Google hates widescreens by Anonymous Coward · · Score: 0

      My biggest gripe with Chromium (wouldn't touch Chrome with its bundled malware with a ten foot pole) is that it does not conform to my UI. There is no reason it should not appear just as every single other window does.

    3. Re:Google hates widescreens by omfgnosis · · Score: 1

      My biggest gripe with Chromium is that it does not conform to my UI.

      That's a good gripe. It's mine too. My gripe isn't so much about appearance (which is increasingly familiar on the Mac) as it is about behavior and interaction expectations. I expect certain behavior of tabs ("move tab to new window"), keyboard (including accessing keyboard shortcuts and the rest of the document even if currently focusing a plugin "frame"), find (Chrome stops highlighting found results after a refresh, unless you cancel and reopen the find panel). I'm fine with the visual differences—in fact, there are good innovations I wish the Mac would adopt, like spoof-proof warnings/notifications. I just can't use Chrome without thinking about how Chrome is different, and that's a sign of a bad UI citizen.

      There is no reason it should not appear just as every single other window does.

      Now this... of course there is. There are a lot of reasons. Few applications have to serve the needs a browser does, and no pre-mobile/pre-ChromeOS operating systems were built with those needs in mind. That isn't to say a good browser can't fit in, but we're far from a point in time where a browser simply has to implement some library features to do everything it needs to do. No OS/WM (as far as I'm aware) implements a tab system with the features any modern browser provides. Every major browser implements toolbar features not available in the core OS/WM. Some are better at fitting in than others (Chrome/Chromium probably being the best, despite being highly customized). But asking for a completely non-descript UI from a browser, at this point, is asking for something akin to IE 6's UI: plenty familiar and native, but barely able to fill the needs of browser users (and IE 6 had the benefit of a Windows task bar that was basically its "tab manager"... this is basically no longer a possibility for any browser).

    4. Re:Google hates widescreens by Anonymous Coward · · Score: 0

      Now this... of course there is. There are a lot of reasons.

      You have not provided a single legitimate reason.. Every other major browser (including other Blink and WebKit based browsers) conforms, except Chromium.

    5. Re:Google hates widescreens by omfgnosis · · Score: 1

      I provided a bunch of reasons. Tab behavior, toolbar behavior being the most substantial.

      Maybe we're talking past each other. I'm not aware of any Blink or WebKit browser that isn't heavily customized from its native environment (including Safari, which has the fewest excuses). Can you say more about what you expect and what violates those expectations?

    6. Re:Google hates widescreens by Anonymous Coward · · Score: 0

      Maybe we're talking past each other. I'm not aware of any Blink or WebKit browser that isn't heavily customized from its native environment (including Safari, which has the fewest excuses). Can you say more about what you expect and what violates those expectations?

      Opera 12 (Presto), Opera (Blink), QupZilla (WebKit), Midori (WebKit) and Firefox (Gecko) all conform to my UI. The expectation is that all UI elements in Chromium should inherit the currently selected Windows theme. I don't have the problem you described with your Mac, since all of the browsers behave as any other standard application window.

    7. Re:Google hates widescreens by omfgnosis · · Score: 1

      What does it mean to "conform to my UI"? Why are you listing rendering engines (which, apart from Firefox, are literally not involved in windowing UI at all)? Are you just talking about adopting appearance characteristics of a windowing theme? Because if that's the case, I definitely misunderstood. I was talking about browsers (all of them) adopting UI conventions that are at odds with (every) environment, often for the better but sometimes not so much.

      But basically, I wasn't talking about appearance convention... and if that's what we're supposed to be talking about, I can single out Firefox\ as far and away the worst offender on the Mac, and pretty much guaranteed never to look or feel native in any way. It probably feels just as foreign as Chromium does on whatever WM you use. The damn thing has never even used native menus EVER, and they're just there, free for the taking!

    8. Re:Google hates widescreens by Anonymous Coward · · Score: 0

      What does it mean to "conform to my UI"?

      UI stands for "user interface", which are the visualizations you see when interacting with a graphical shell. If something does not conform to the UI, that means it has its own UI that doesn't fit in.

      Why are you listing rendering engines (which, apart from Firefox, are literally not involved in windowing UI at all)?

      Because that is what the browser is. The UI portion is peanuts, as proven by the fact that ONLY Google has screwed this up. Nobody else has.

      I was talking about browsers (all of them) adopting UI conventions that are at odds with (every) environment, often for the better but sometimes not so much.

      In Windows I don't have this problem. Every browser works pretty much like any other application, menus are where they should be, shortcuts are corrects, etc. The UI itself is an eyesore though and it's annoying to have just the one application that doesn't look right. It also makes it pretty much impossible to read some text in the UI due to conflicting colour schemes.

    9. Re:Google hates widescreens by Hognoxious · · Score: 1

      Slashdot hates all screens. Gotta love that horizontal scrolling!

      --
      Confucius say, "Find worm in apple - bad. Find half a worm - worse."
    10. Re:Google hates widescreens by gl4ss · · Score: 1

      well the mac app-menu-at-top-of-screen is just stupid if there's multiple apps in view at a time...

      --
      world was created 5 seconds before this post as it is.
    11. Re: Google hates widescreens by Anonymous Coward · · Score: 0

      Neither Firefox note Internet explorer conform to the visual look on Windows by default. Firefox has that big orange "Firefox button" that all of its menus are hidden behind, just like Chrome's menu button.

      A user can MAKE Firefox look pretty much like it natively should, but there's still quirks. Chrome and IE are both simply out of place no matter what you do, and IE is developed by the vendor! ... lastly
      Um... Browsers aren't browser engines. Blink is the HTML engine only, for example. There's also the JavaScript engine (Chrome uses V8) and UI. Both Opera and Chrome use the Blink layout engine and V8 JavaScript engine and wrap them in completely unique UIs. In a discussion about UI, only the UI part matters. If browsers were layout engines, you'd hate Opera just as much as Chrome.

    12. Re:Google hates widescreens by omfgnosis · · Score: 1

      UI stands for "user interface", which are the visualizations you see when interacting with a graphical shell. If something does not conform to the UI, that means it has its own UI that doesn't fit in.

      I beg your pardon. UI stands for user interface, which is the way a user interfaces with an application. Yes, that includes appearance, but it is far from only that. The behaviors of menus, cursor interactions, focus, stacking, direction of elements, language, are all factors in a UI. Even vague things like "feel" which includes such nit picks as which elements of an interface respond to interaction while in the background, how a caret moves through a text field, what portions of a window are draggable. All of this and more is user interface.

      Because that is what the browser is. The UI portion is peanuts, as proven by the fact that ONLY Google has screwed this up. Nobody else has.

      And you listed other browsers using the same rendering engine as Chrome, so clearly the rendering engine has fuck all to do with the UI.

      In Windows I don't have this problem. Every browser works pretty much like any other application, menus are where they should be, shortcuts are corrects, etc. The UI itself is an eyesore though and it's annoying to have just the one application that doesn't look right. It also makes it pretty much impossible to read some text in the UI due to conflicting colour schemes.

      I'm pleased you see this much UI conformity in Windows. My experience on Windows is not the same, but I am also considering a much broader set of expectations (as listed above).

      To clarify this entire conversation: we had a misunderstanding about what you meant by "UI", and diverged from there. Obviously Chrome looks out of place in some environments, because it has a fairly distinctive appearance of its own. Yes, I agree it can be annoying. But my point was that every current browser does unconventional things in their UI, because the UI toolkits available to them are too limited for the needs of a good browser interface. I hope we can agree that is the case as ell?

    13. Re:Google hates widescreens by omfgnosis · · Score: 1

      That isn't what I meant by native menus, and Firefox does actually use *those*. What I meant is that menus rendered for selects/dropdowns/context are fakes that neither look nor behave as a Mac user expects.

      As far as where a menu bar in an OS belongs... More often than not, it doesn't belong anywhere. If your application needs to provide so many operations that it needs to hide many of them in a multi-dimensional listing, your application either does too much or is poorly designed for user interaction. There are some (few) exceptions to this, but for most purposes menu bars should be considered legacy UI elements providing redundancy for users who expect every operation to be catalogued in a single place. Their primary function at this point is to provide a visual listing of all of the (also hopefully few) keyboard combinations available. If this approach is taken, it does not matter where the menu is positioned.

    14. Re:Google hates widescreens by StarFace · · Score: 1

      Oh please. Unless you want a world full of foolish "apps" instead of honest to goodness software that can actually do more than three things, getting rid of menus is woefully stupid. It's not "hiding" commands to put things in menus. The menu system is an extremely efficient triggering and referencing system, as efficient to use with a mouse as a keyboard. It makes everything easy to find, not hard.

      That is not to say that every program needs a menu, but they are the exceptions. Serious software with anaemic menus is not even worth the download bandwidth and are deleted from my computer promptly. That includes crappy consumer oriented browsers like Chrome.

      --
      V
    15. Re:Google hates widescreens by omfgnosis · · Score: 1

      Funny, when I download software with lots of stuff in menus, I usually view it as stuff like this: http://www.uxdesignedge.com/wp...

      I'd much prefer many small programs that do very few things, very easily and very well; versus large programs that try to be everything to everyone. Incidentally, that is also the unix philosophy.

    16. Re: Google hates widescreens by Anonymous Coward · · Score: 0

      I don't know what you're talking about. My Firefox v36 fits flawlessly in with the look of my desktop. As for IE, not sure if you're trolling or your system is just whacked, but IE obviously fits in, as it is part of the OS.

      Yes, browsers *are* browser engines. That is the core and the single largest and most important piece of any browser, which is why there are so many browsers based on the same cores. The UI is only a trivial part of the equation and are easily created as proven by every single other browser besides Chrome.

      Sorry to take you down a few pegs, but you really don't have a clue, kid.

    17. Re:Google hates widescreens by Anonymous Coward · · Score: 0

      I beg your pardon. UI stands for user interface, which is the way a user interfaces with an application. Yes, that includes appearance, but it is far from only that. The behaviors of menus, cursor interactions, focus, stacking, direction of elements, language, are all factors in a UI.

      And all of those things are invisible elements that you require zero feedback from? Read what you said and get back to me when you figure out what is wrong with it.

      The only browser I have installed that looks unconventional is Chromium. Neither version of Opera, Firefox Nightly, Midori or QupZilla have this problem.

    18. Re:Google hates widescreens by omfgnosis · · Score: 1

      And all of those things are invisible elements that you require zero feedback from? Read what you said and get back to me when you figure out what is wrong with it.

      Not all, but they're all expressing more than just a pixel configuration on a screen.

      The only browser I have installed that looks unconventional is Chromium. Neither version of Opera, Firefox Nightly, Midori or QupZilla have this problem.

      Yeah, okay. Glad we've reached the endless repetition portion of this conversation. Cheers!

    19. Re:Google hates widescreens by Anonymous Coward · · Score: 0

      Here's a thought, genius: Don't want repetition? Then stop stating things that have already been refuted as if repeating them will make them come true. Seriously, you're like the little kid who plugs his ears and screams "lalalalalalala I can't hear you".

    20. Re:Google hates widescreens by omfgnosis · · Score: 1

      Yeah okay, "UI" just means how a thing looks and Chrome is uniquely terrible. Goodness forbid I try to expand the conversation a little without it being an all-or-nothing debate.

    21. Re:Google hates widescreens by Anonymous Coward · · Score: 0

      *facepalm* There you go, repeating again.

      UI does just mean how something looks. The term you are so desperately searching for is "UX".

      And I'm not sure how you were trying to expand the conversation when you didn't even understand what was going on.

    22. Re:Google hates widescreens by omfgnosis · · Score: 1

      Look. I won't even appeal to my own authority, as a software developer with over a decade of UI experience. I'm sure you're also an experienced developer with UI chops, and I don't want to have a bigger dick contest. Instead, check this out: http://en.wikipedia.org/wiki/U... - it's actually a pretty decent article for Wikipedia, and may be helpful in understanding what I was talking about (if you have any interest in understanding what others are talking about, instead of just trying to be "right" on the Internet).

      Have a nice day.

    23. Re:Google hates widescreens by StarFace · · Score: 1

      I'd much prefer many small programs that do very few things, very easily and very well; versus large programs that try to be everything to everyone. Incidentally, that is also the unix philosophy.

      Yes, but as you know, that philosophy of a thing doing one thing well, is a statement on the scope of any particular piece of software, not its depth or capabilities. A program can, and likely should, go to whatever depth is necessary within its scope. If I want to do some serious text editing, I want a deep text editor like Sublime or gVim, not something like TextEdit or Notepad.exe. Some people can get by with those all right, and indeed I use simple programs like that if all I need is to quickly change a typo in a .txt file--but often I need more. All of these examples are text editors, they have a similar narrow scope, their "thing", they stick with what they should be doing and nothing more--however there is a huge difference between Notepad.exe and gVim when it comes to depth within that scope.

      I don't get your screenshot though, how is this supporting your case? That seems, actually, to be a prime example of a utility that would really benefit from a few menus! I mean, this is exactly why menus are a good thing. Look, they even waste space with buttons for "Exit", "Save" and Load! What a waste of space and mental serenity. Bad as that is though, I don't see anything here that would classify as being out of scope, or example of software that is trying to do too many things. All of these are integral to the function of page scouring--one thing--and thus good example of a narrow scope with depth (as would be wget, the underlying engine behind this particular front-end).

      I shudder to think what is behind that "Pro Mode" though. Ha.

      --
      V
    24. Re:Google hates widescreens by omfgnosis · · Score: 1

      My text editor (I prefer TextMate, but Sublime shares a lot of its roots with TM) is another one with lots of menu stuff. Truth be told, 90% of it could go away and I'd never notice (because I am only coding in a handful of languages and don't need a universal editor all of the time). But I think these complex tools are an exception, and I would not provide tools like that to the vast majority of people who are better served by a simple editor like TextEdit (which is far simpler, but also far more powerful than Notepad).

      That seems, actually, to be a prime example of a utility that would really benefit from a few menus!

      Oh come on, this is just brushing the problem under the rug. You're moving all of that complexity out of view, but you're not removing it. Making HTTP requests is hardly a complex thing for a user. I do it with my web browser all the time without having to check a single checkbox ever. The whole example is kind of contrived, but the point is that engineers design poor UIs. Whether those UIs are visible or tucked away to be less discoverable is hardly material. The fact that it's a front-end to wget points to the fact that the UI of the underlying command prompt is the source of the design problem, and that has neither menus nor checkboxes! They're all fundamentally the same UI, just presented (or not) slightly differently.

      Making software simple to use is quite hard, but it's worth doing, and it doesn't mean the software is not powerful or useful. It's the difference between computing being accessible to everyone versus reserved for people who have spare time or resources (like income) to dedicate to it.

    25. Re:Google hates widescreens by StarFace · · Score: 1

      But I think these complex tools are an exception, and I would not provide tools like that to the vast majority of people who are better served by a simple editor like TextEdit (which is far simpler, but also far more powerful than Notepad).

      That's fine, nobody is saying that everyone needs Maya. You were saying, however, that menus are a sign that a program is "too complicated", and to that I strongly disagree.

      Menus are an important aspect of a program's accessibility, this is especially true on a Mac! Menus are fundamental to the architecture of the system, and programmers are encouraged to replicate all important functionality within them for this reason. They allow the handicapped access to functions that might be otherwise difficult or impossible to navigate to using stepwise controls, tongue sticks for the quadriplegics, voice commands, Braille systems, or VoiceOver. For beginners and intermediate users, they provide training wheels toward learning keyboard shortcuts and what the software is capable of. They make the Help menu more useful as you can search for features using common language. For power users they provide extensive automation hooks (especially where there is no AppleScript dictionary) and customisation since on a Mac, menus are fully keyboard customisable.

      This stuff is useful, even essential, from Stickies on up. Just because you don't need it doesn't mean the software doesn't either, as a tool for many. You don't know how I use a computer, I don't know how you use yours. You can't make assumptions about design based on your usage patterns or preferences.

      Oh come on, this is just brushing the problem under the rug. You're moving all of that complexity out of view, but you're not removing it.

      You misunderstand me. Part of the problem with the UI you posted a link to is that because of the irrational fear of using menus, they have had to relocate bog standard application control functions as permanently visible buttons. By simply adding a File menu and a Help menu, you could remove 25% of the clutter in this screenshot. Next, some of these things are clearly configuration related, rather than something you need constant access to, such as proxies. They can be located in menus as toggles, or in a preference window.

      The answer isn't to strip out all of the features, but to create a design that supports the features, and part of that is putting standard (such as File:Quit) or seldom-used stuff (like links to a web page) into menus.

      The fact that it's a front-end to wget points to the fact that the UI of the underlying command prompt is the source of the design problem...

      I don't really follow that argument. Modern CLI is as much for automation as it is for the user. Geeks use this stuff to build complex toolchains and to configure systems for unattended operation. Think of command-line flags as a sort of "API" and you're closer to the truth. Since commands are simple text strings, they can be constructed programmatically, parsed and dropped into anything that can store text.

      How a user-land GUI approaches the underlying tool has nothing to do with the underlying tool's "API" save for its core feature breadth (though there is much you can do on top of an API of course). It's the responsibility of the programmer/designer to turn the raw functionality of the tool into a system that humans can interface with efficiently.

      The whole example is kind of contrived, but the point is that engineers design poor UIs.

      Indeed, to the point that it doesn't serve your argument well at all. A front-end to wget is hardly an example of something that needs to be made as simple as TextEdit. It's a power tool to start with, and the basic goal of it is in itself a complex task, so much so that you'd have to describe what it even does to the average person who doesn't conceptu

      --
      V
  2. Tabs on side?? How about tabs on BOTTOM. by markdavis · · Score: 3, Insightful

    Meanwhile, Firefox takes away the choice for users to have tabs on bottom (below the menu bar and bookmark bar) , like many want. Since Mozilla now has SUCH a desire to be EXACTLY like Chrome, it should be no surprise they would remove user choice, and even add an annoying and identical menu button on the right.

    Thankfully, for now, you can get sane behavior back with the "Classic Theme Restorer" add-on. Yet again, Add-on's save the day and show off one of Firefox's main strengths. Back to Chrome- who knows, maybe they will start adding user choice?

    Considering how important browsers are to a user's computer experience, I fail to understand why Chrome is so hostile to customization and why Mozilla is following that same path now. Let users put things where they want them (at least without artificial limits), and don't take away existing customization options!

  3. No foolin? by Anonymous Coward · · Score: 0

    You mean I could be a unpaid Google employee? Where can I sign up?

    1. Re:No foolin? by Anonymous Coward · · Score: 0

      No one ever got rich by writing a lot of checks. Take what you can. Give nothing back.

  4. Chrome needs load tabs on demand. by zixxt · · Score: 1

    My favorite feature of Firefox is load background tabs on demand, its a shame other browsers do not have this. I can start up Firefox with 200 tabs from the previous session and it starts up nice and quick, with other browsers if I did this I could go make a pot of coffee and it browser would still be loading when I came back.

    --
    ---- GENERATION 26: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
    1. Re:Chrome needs load tabs on demand. by Anonymous Coward · · Score: 0

      most would happily trade the rarely used feature of being able to have a crap load of tabs opened in the background for a stable browser that doesn't explode when a single tab dies. This is part of the problem with firefox, they focus on bloat for the few while not fixing the core product problems.

    2. Re:Chrome needs load tabs on demand. by Anonymous Coward · · Score: 0

      After setting flash to click to play I've literally never seen a tab die or a browser crash.

    3. Re:Chrome needs load tabs on demand. by circletimessquare · · Score: 1, Informative

      i used to do that

      i discovered chrome has a "bookmark all tabs..." option if you right click on any open tab

      pick a location for the folder (i have a top level folder full of 9 numbered folders, so it's chronological)

      done

      so after 20-30 open tabs, i bookmark all, flush all open tabs, and move on with a much saner life

      you should as well

      --
      intellectual property law is philosophically incoherent. it is your moral duty to ignore it or sabotage it
    4. Re:Chrome needs load tabs on demand. by Anonymous Coward · · Score: 2, Informative

      I use Tab Snooze for that in Chromium. It works much better than Firefox's solution because it frees up all of the RAM used by the tabs until they are needed.

    5. Re:Chrome needs load tabs on demand. by DMUTPeregrine · · Score: 1

      Except that a single tab pretty much never dies. I've not had that happen for quite a while now.

      In fact, it stopped happening about the time I uninstalled all plugins (flash, Java, etc). Probably not a coincidence. I use Chrome for the few things that need Flash, which is thankfully getting even rarer these days.

      --
      Not a sentence!
    6. Re:Chrome needs load tabs on demand. by Anonymous Coward · · Score: 0

      The new Opera can do this.

    7. Re:Chrome needs load tabs on demand. by Anonymous Coward · · Score: 0

      i discovered chrome has a "bookmark all tabs..." option if you right click on any open tab

      Firefox has this feature as well, which I didn't know about until I read your comment and checked to see if it did. I'll be using this. Thanks!

    8. Re:Chrome needs load tabs on demand. by drinkypoo · · Score: 1

      I use Tab Snooze for that in Chromium. It works much better than Firefox's solution because it frees up all of the RAM used by the tabs until they are needed.

      Does Firefox allocate the memory for tabs before you click on them? It doesn't seem like it.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    9. Re:Chrome needs load tabs on demand. by Anonymous Coward · · Score: 0

      My favorite feature of Firefox is load background tabs on demand, its a shame other browsers do not have this. I can start up Firefox with 200 tabs from the previous session and it starts up nice and quick, with other browsers if I did this I could go make a pot of coffee and it browser would still be loading when I came back.

      Okay, serious question: why on Earth do you need that many tabs on startup? Or why would you need that many tabs open at once? Even if it took you one minute to check out all the new stuff in a tab since the last time you looked at it, you're still looking at nearly three and a half hours just doing that. Surely there's a point where it's going to be faster to do a web search for whatever it is you're looking for instead of trying to remember that it's in Tab 134.

    10. Re:Chrome needs load tabs on demand. by RebelWebmaster · · Score: 1

      There's a little bit of overhead for each blank tab. You can see it in about:memory if you're interested.

    11. Re:Chrome needs load tabs on demand. by Anonymous Coward · · Score: 0

      I just ran a test. Loading Firefox with five tabs, where only one tab has loaded, puts me at around 400MB RAM usage. Loading Firefox with only a single tab, the same one that was loaded before, it's 275MB.

  5. a company stepped up to do it by raymorris · · Score: 3, Interesting

    I see a company stepped up to do it. Google decided it wasn't what they wanted to spend their time on, but they were willing to accept it if someone else found it useful enough to do do it. Benjamin said his company will do it, so it should happen.
    https://code.google.com/p/chro...

  6. Use Pale Moon by HBI · · Score: 1

    Seriously, it's better.

    --
    HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
    1. Re:Use Pale Moon by Bing+Tsher+E · · Score: 1

      Use SeaMonkey. It's the same Mozilla codebase, but with traditional features like built in HTML editor, email, newsreader.

    2. Re:Use Pale Moon by omfgnosis · · Score: 1

      Use Netscape Communicator, for bonus retro points!

    3. Re:Use Pale Moon by Anonymous Coward · · Score: 0

      I use Netscape Navigator, you insensitive clod!

    4. Re:Use Pale Moon by zixxt · · Score: 1

      Seriously, it's better.

      Umm no its not. It's a hacked together outdated fork that is slower and more crash prone than Firefox plus a ton of add-ons do not work with it.

      --
      ---- GENERATION 26: The first time you see this, copy it into your sig on any forum and add 1 to the generation.
    5. Re:Use Pale Moon by Anonymous Coward · · Score: 0

      What the fuck did you use? I found it's more stable and faster, and it's not really out-of-date. Some poorly-made add-ons probably don't work, though.

    6. Re:Use Pale Moon by Anonymous Coward · · Score: 0

      >but with traditional features like built in HTML editor, email, newsreader.

      So built-in bloat that no one wants

    7. Re: Use Pale Moon by Anonymous Coward · · Score: 0

      I like there being an 'edit' menu choice in the menu of my web browser. It makes it easy to work on local copies of my web content. Sure, it's considered reactionary for 'users' to be able to edit web content, but it sure makes it easier to save an editable local copy of web content.

      Probably it's considered wrong, possibly even illegal, by some "content providers." They prefer the removal of menus and menu options. Let Google steer us toward our future.

      When did anybody start to get away with that kind of shit on Slashdot?

    8. Re:Use Pale Moon by Anonymous Coward · · Score: 0

      It's someone taking Mozilla's hard work and rebranding it with very minor tweaks and changes. But the placebo effect is far too strong to ignore, so you'll regularly hear "it's better" when in reality you'll get the same results (or better) by switching to the nightly 64-bit builds and resetting your profile. Of course that means having to use the new UI, which a lot of people insist is better despite it having a lot of problems that will drag Pale Moon down to its death at this rate. Or Pale Moon will just pretend they're heros and not adopt new features like Electrolysis or MSE, because it's easier to not do things and take credit for that.

    9. Re:Use Pale Moon by HBI · · Score: 1

      Some poorly-made add-ons don't work with Firefox itself, either.

      --
      HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
    10. Re:Use Pale Moon by Anonymous Coward · · Score: 0

      It's someone taking Mozilla's hard work and rebranding it with very minor tweaks and changes.

      Uhh, Mozilla stole this feature from Opera and now Chrome will too. Mozilla has NEVER done anything innovative, they just copy from superior browsers.

  7. Neat Idea by Anonymous Coward · · Score: 1

    Tree-style browser tabs are a neat idea. It's not very often where I'm searching for a piece of information and end up with more browser tabs than I can keep track of, but I could see how this would be a very useful feature.

    It is too bad that the Firefox project has been derailed by "developers" more interested in "contributing" UI changes than actual bug fixes to the point where I'm no longer willing to use it, or I'd go fire up Firefox and check out the tree-style tab plugin.

    1. Re:Neat Idea by wiredlogic · · Score: 1

      I use it all the time. Scan through Hacker News and right click open all the interesting headlines and comment sections then browse the fully rendered pages at my leisure. This is much more practical with a hierarchical vertical strip.

      --
      I am becoming gerund, destroyer of verbs.
    2. Re: Neat Idea by Anonymous Coward · · Score: 0

      Why not middle click?

  8. Typical abuse of unpaid opensource devs. by danknight48 · · Score: 3, Insightful

    if someone from the open source community would step forward to do the work to drive the feature to completion.

    Google/Chromium paid devs can then take all the credit. One sided deal if you ask me.

    1. Re:Typical abuse of unpaid opensource devs. by thegarbz · · Score: 5, Insightful

      Sounds more like "if you want it do it yourself" via extensions.

      That seems like a perfectly reasonable approach for something a company doesn't want to focus on.

    2. Re:Typical abuse of unpaid opensource devs. by Anonymous Coward · · Score: 0

      Or the motivated Open Source coder gets offered a job at Google ...

    3. Re:Typical abuse of unpaid opensource devs. by Anonymous Coward · · Score: 0

      In my opinion they did a quite fair offer.

      They are basically saying "This is not terribly important ourselves as a main feature, but patches are welcome to make this possible as a side feature for those who want it."

      At the end of the day, it's their product.

    4. Re:Typical abuse of unpaid opensource devs. by Anonymous Coward · · Score: 0

      We need one strong "true community" fork that is hosted and supported by volunteers that will focus on "wontfix" bugs that tie the chromium browser project too tightly to google.com. Until this happens, the chromium "community project" is basically a joke at best, and a slap in the community's face at worst.

    5. Re:Typical abuse of unpaid opensource devs. by JackieBrown · · Score: 1

      if someone from the open source community would step forward to do the work to drive the feature to completion.

      Google/Chromium paid devs can then take all the credit. One sided deal if you ask me.

      This is a sad response to read on slashdot.

      What do you think would be a good reason for a company to opensource their development if not for stuff like this? It fits perfectly in the matra "If i had the source, I could make it work the way I wanted."

    6. Re:Typical abuse of unpaid opensource devs. by AvitarX · · Score: 1

      I doubt it, if they are asking for it to be made as an extension, then the extension writer would get the credit.

      --
      Wow, sent an e-mail as suggested when clicking on "use classic" banner, and got a fast response that addressed my msg
    7. Re:Typical abuse of unpaid opensource devs. by Anonymous Coward · · Score: 0

      That might fly if Google had the only game in town, but they don't. If you think I'm going to waste my time fixing Google's shit for them instead of just using someone else's browser that already works, then you're crazy.

  9. Google in deep poverty, needs community funding by Anonymous Coward · · Score: 1

    I have a different idea: how about Schmidt putting slightly more pocket change into his browser team instead?

  10. It's been extended already by mentalfloss · · Score: 1

    Er, I've had this solution (at least as a UI) in extension form: https://chrome.google.com/webs...

    --

    ----
    http://mentalfloss.ca - Free music that doesn't suck
    1. Re:It's been extended already by Andtalath · · Score: 1

      Seperate window.
      It's an ugly work-around which disrupts focus workflows.

    2. Re:It's been extended already by QuasiSteve · · Score: 1

      I'm more partial to Tabs Outliner. It's also a separate window, but it's modeless so it just lives to the left of my browser window.

      It's still an ugly work-around, but when stuck with Chrome it's better than nothing.

  11. Get with the times by Trogre · · Score: 4, Interesting

    After using Tree Style Tab (combined with Tab Mix Plus) for over three years now I can't imagine going back to tabs-on-top on a widescreen monitor *shudders*.

    Never mind the better use of real estate, the hierarchichal nature of the tabs (the "tree" in the name) is just brilliant.

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
    1. Re:Get with the times by dragoneye1589 · · Score: 1

      This extension is one of the few reasons I'm still using Firefox, the browser has gotten pretty terrible of late. This was a feature that Opera lost during the move to WebKit as well.

    2. Re:Get with the times by Anonymous Coward · · Score: 0

      If you are up for alternatives to Firefox, Palemoon is a fork of it from before the UI turned to poo. Most Firefox extension I have tried with it work for me, including Tree Style Tab.

    3. Re:Get with the times by chooks · · Score: 1

      Sib AC is correct. I have been using palemoon with tree style tabs for well over a year. No problems.

      Palemoon overall has been a good experience. It is relatively stable (maybe a couple of crashes in a history of heavy heavy use) and speedy. It is worth checking out if you haven't already.

      --
      -- The Genesis project? What's that?
  12. Summary is wrong. by Anonymous Coward · · Score: 0

    He says that a tree-style interface for tabs would be overly complex as a native implementation,

    No the actual post says that it doesn't meet a cost-benefit analysis. Complexity is an aside.

    A correct summary would read

    He says that Google isn't willing to pay for this development to take place

  13. Re:Tabs on side?? How about tabs on BOTTOM. by aix+tom · · Score: 2

    I just defected to Pale Moon two month ago.

    Absolutely brilliant. Firefox as it used to be. Configurable like it was in the good old days, with that Australis interface ripped out. (And even returned to a sane version numbering scheme lately).

    TreeStyle Tab works for vertical tabs (in contrast to SeaMonkey, where it doesnt), and with "Firefox 3 Theme for Firefox 4++ Reloaded" it works, looks and behaves exactly as the Firefox did in its best days. I finally feel "at home" again on the Internet without being irked by unexpected UI surprises all the time.

  14. how about smooth scroll + W3C standards by Billly+Gates · · Score: 1

    IE 11 you hit up or down arrow keys. Smooth as butter like a phone. Firefox mostly as smooth as its XP hooks limits hardware acceleration.

    CHROME? Blip blip blip tear in image when you hit up and down. Slashdoters on Windows reading this try it? Surprised?

    First Chrome had it. Then you had to go into about::flags. Now it is not even available? WTF. IE 8 in 2009 had this and Firefox in 2011. I can't even use it anymore as it feels like I am on an old computer. I hope someone from Google is reading this.

    Last blink is not standard compliant. Font face, animations, and other things are not done like W3C. I have to write one site for W3C compliant browsers and one conditions for blinks way of doing things. It reminds me of IE of old

    1. Re:how about smooth scroll + W3C standards by Anonymous Coward · · Score: 0

      IE 11 you hit up or down arrow keys. Smooth as butter like a phone.

      IE has also the most responsive and smooth touchpad and touchscreen scrolling.

    2. Re:how about smooth scroll + W3C standards by Anonymous Coward · · Score: 1

      Ugh - god no. Smooth scrolling hurts my eyes.

      I want my computer to be instantly responsive. I want my scrolling to be immediate. I do not want to waste that 0.2 seconds it takes for the page to animate into position whenever I use my scroll wheel or click in the scroll bar or press pageup/down. The page content should completely update in between monitor refreshes in my opinion. For all the reasons I hate Chrome, a lack of smooth scrolling is not one of them.

      If I wanted a smartphone experience - I'd grab mine. Otherwise keep your touchscreen friendly bullshit off my PC.

    3. Re:how about smooth scroll + W3C standards by Anonymous Coward · · Score: 0

      >Otherwise keep your touchscreen friendly bullshit off my PC.

      This is always good advice. That fucking OSX update where windows started doing the smartphone rubberband thing? Fuck that. I'm glad it was possible to disable, because that and "natural scrolling" are abominations.

    4. Re:how about smooth scroll + W3C standards by Anonymous Coward · · Score: 0

      This, so much this.

      I turn my "delay times" for everything down to the lowest they will go, outside of the obvious things like double click.
      I'm not 1700, I don't find instant UI popping jarring.

      There was only one acceptable smooth scrolling, a dead Firefox extension I no longer remember the name of that had mouse gestures that were the best. The middle click scroll was replaced by one that made the entire viewport a percentage representation of the space taken up by the document, so you could scroll really quickly around.
      It had such smooth scrolling as well. It even ran on my now (and current about to be replaced) 8 year old machine. Funnily enough if it existed in current Firefox, it would probably run like crap and take up infinitely more memory on levels as bad as adblock with an even reasonably large list.

      I even hate the smooth scrolling crap on phones as well.
      So often it is implemented horribly.

    5. Re:how about smooth scroll + W3C standards by Anonymous Coward · · Score: 0

      Wait, you LIKE the jerky, buggy scrolling in Chrome? I prefer my browser to scroll smoothly instead of chop-city making you lose your place like Chrome does.

      It's like comparing 60 FPS to 10 FPS. Buttery smooth or choppy slideshow? I suppose it's not much of a surprise. Put a Windows phone and an Android phone side by side and start scrolling. Windows phone is always silky smooth and responsive while Android is a jerky, halfway unresponsive mess.

  15. Worse is better, so Chrome won by Kohlrabi82 · · Score: 1

    There once was a browser which supported this out-of-the-box several years ago.

    RIP, Presto-Opera

  16. So behind... by Anonymous Coward · · Score: 0

    Amazing! Even now, modern browsers are still catching up with features Opera had a decade ago!
    (The real Opera, not this travesty that is Chrome wearing its corpse like a second skin)

  17. Side tabs should be default by labnet · · Score: 1

    I used the side tab in chrome before it was dropped. As soon as it was dropped I deleted chrome from my system. Every PC I setup for anyone has Firefox with side tabs. I can have over 50 tabs open and it's the only sensible way to navigate on a 16:9 screen. There is a forum that discusses this, and the engineer who dropped it says very few used it. Well duh: you had to execute obscure commands to even enable it. Side tabs should be the default mode for any browser.

    --
    46137
    1. Re:Side tabs should be default by Anonymous Coward · · Score: 0

      This.

      I was PISSED when that prick in the Chromium Dev discussion axed it. It was one single person that was so heavily against it and I cannot remember his name any more because I try to forget annoying things rather than let them grow.

      It is absolutely not an issue. It isn't any more complicated than the current tab bar. In fact, the current one is a literal hack to get it like that, it is more effort than a typical title bar. So they can't say shit about complicated.
      Vertical tabs worked. Tree-style, yeah, that would have been more of an issue, but it would still be easily possible.
      A true sidebar instead of that SHIT little bubble window that extensions get now? Infinitely better. Why it has seriously taken this long to get a sidebar is beyond me.
      That crap bubble pop-up is useless for anything of worth. Worst thing about it is if you try to interact with it and a tab at the same time, hey, good luck with that, it is impossible since there is no always-show flag, as soon as it is inactive, DEAD, gone, along with possibly anything you were doing and now you need to do it again. Sidebars are permanent and don't suffer this atrocious issue THEY still continue to make.

    2. Re:Side tabs should be default by Anonymous Coward · · Score: 0

      He was right. Most people don't have 50 tabs open at once and if you're only viewing a single page or two, then that's an awful lot of wasted space being used for vertically stacking tabs.

  18. What about faceted tag clouds for bookmarks? by SpzToid · · Score: 1

    How do you folks deal with thousands of bookmarks? You do tag them right? Firefox's tagging facility has been able to do this for awhile, but then how does that reduce the sheer quantity, to something user-friendly? There's a decent but semi-broken extension for this also, called Tag Sieve. There's also been a feature request made to build it into FireFox native, and I hope the original developer gets the job. In the meantime, having read the user-comments, I've made the extension work, and it is wonderful. Highly recommended.

    https://addons.mozilla.org/en-...

    https://bugzilla.mozilla.org/s...

    --
    You can't be ahead of the curve, if you're stuck in a loop.
    1. Re:What about faceted tag clouds for bookmarks? by drinkypoo · · Score: 1

      How do you folks deal with thousands of bookmarks? You do tag them right?

      What? I organize them hierarchically, like I've been doing since Netscape Navigator.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    2. Re:What about faceted tag clouds for bookmarks? by Anonymous Coward · · Score: 0

      I save them to an RTF in Wordpad. No, I am not kidding. I type the websites' name and a few keywords. I press Control+F to search for bookmarks. In Windows 8, I can click the blue text to open the website in my web browser.

      example entry in bookmarks.rtf:
      Slashdot - news for geeks
      http://www.slashdot.org

      I know, using actual bookmarks in the cloud or web browser is easier than using a text file. I don't know why I still copy URLs from a text file though. *scratches head* The file is 400 kilobytes in size. I don't know how many lines long it is (including the blank lines).

      Why am I posting my story? You asked for it. *smile*

    3. Re:What about faceted tag clouds for bookmarks? by Anonymous Coward · · Score: 0

      How do you folks deal with thousands of bookmarks?

      The same way I deal with thousands of files: folders. Tags are annoying, they just waste time having to apply them and trying to remember what you tagged with what. Folders are infinitely more efficient.

  19. Re:Tabs on side?? How about tabs on BOTTOM. by Anonymous Coward · · Score: 0

    That's just a different side. How about tabs in the middle?

  20. Interface choices by sjbe · · Score: 1

    well the mac app-menu-at-top-of-screen is just stupid if there's multiple apps in view at a time...

    Why? You cannot physically perform actions on more than one app at a single time. The menu is active for the one you are presently using as indicated by where you have clicked the mouse pointer. It's not the only way to do things (or even necessarily the best) but it's perfectly sensible and logical and consistent.

    What annoys me about the mac interface is that choosing the close window button on the window frame doesn't actually close the app if there are no windows left open. I have to either close the app from the pull down menu (two clicks) or use a keyboard shortcut. I have never once wanted to close all the windows of an app and still leave the app running. It' just not an interface choice I truly grok.

    1. Re: Interface choices by Anonymous Coward · · Score: 0

      Menu as part of app: move mouse horizontally to window to interact with menu.

      Menu at top of screen: move menu horizontally to focus window, then move mouse all the way to the top of the screen to interact with menu.

      Often UI experts try to minimize the mouse travel distance between common actions. Making users run to the top of the screen means you can't put anything remotely common in the menu without duplicating it elsewhere.

    2. Re:Interface choices by drinkypoo · · Score: 1

      I have never once wanted to close all the windows of an app and still leave the app running. It' just not an interface choice I truly grok.

      Think of it like being in MDI mode all the time, in every application. Because that's how the MacOS GUI has worked since time immemorial. You can close all the documents without exiting the app. Back then, it was common for application menus to be provided as a numbered list of options in the middle of the screen, the menu bar is the same thing but now it's at the top of the screen and still available while documents are open. But hey, there are lots of apps which behave the way you seem to want them to behave, they pop up a window with some menu options when you close the last document.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    3. Re:Interface choices by fintux · · Score: 1

      well the mac app-menu-at-top-of-screen is just stupid if there's multiple apps in view at a time...

      Why? You cannot physically perform actions on more than one app at a single time. The menu is active for the one you are presently using as indicated by where you have clicked the mouse pointer. It's not the only way to do things (or even necessarily the best) but it's perfectly sensible and logical and consistent.

      What I hate about the menu location is that on a big screen I have to drag my mouse all the way to the upper left corner, even if the window I'm dealing with is in the lower right corner. Combine that with the lack of decent keyboard navigation for the menus, they are pretty much useless for anything else than looking up the keyboard shortcuts.

    4. Re:Interface choices by fintux · · Score: 1

      Think of it like being in MDI mode all the time, in every application.

      1. MDI doesn't make sense with every application. It works for programs where you have multiple content items and some common tools for them (like an image processing program) or if the application needs for some other reason to have multiple windows open. MDI stands for "Multiple Document Interface", so it's not a coincidence that it works well for such usage, since it was designed for it.

      2. Even MDI applications can be closed by the closing the main window, which you don't have in the OS X applications.

      Because that's how the MacOS GUI has worked since time immemorial.

      Just because it has been that way for a long time doesn't mean that it actually is the optimal solution. It just makes it an old solution.

      But hey, there are lots of apps which behave the way you seem to want them to behave, they pop up a window with some menu options when you close the last document.

      There's a difference: The user closes the last window, the application closes vs. the user closes the last window, the application opens a new window. That is just counterintuitive.

    5. Re:Interface choices by drinkypoo · · Score: 1

      There's a difference: The user closes the last window, the application closes vs. the user closes the last window, the application opens a new window. That is just counterintuitive.

      Well, once upon a time I might have made many of the same arguments. But now, RAM is cheap. I don't mind having the applications lurking around in the background. Not that I even use OSX, but last time I did (for a job) it was not a big deal, because the system had lots of RAM. And it was only 8GB, but it was plenty at the time and for the stuff I was doing, hint, not video.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  21. "Thousands of bookmarks"? Why? by sjbe · · Score: 1

    How do you folks deal with thousands of bookmarks?

    If you "need" to deal with thousands of bookmarks you are Doing It Wrong. Help me out here because I honestly cannot even imagine a (sane) use case or work flow where I would actually need (much less want) to deal with that many bookmarks.

  22. This isn't enough by DrXym · · Score: 1

    I won't be happy until there are tabs on EVERY side at once. And nested as well. How is Chrome supposed to be CUA compatible on OS/2 otherwise?

  23. Re:"Thousands of bookmarks"? Why? by SpzToid · · Score: 1

    No, I'm not doing it wrong. For example, I see tech-notes and answers all the time on stackoverflow.com, so I bookmark and tag them for future reference, so I CAN forget about them. Other forums too, since I am a developer. These add up and can overwhelm quickly otherwise, and become un-useable. Tag Sieve plus the native tools for sorting bookmarks in FireFox make my clippings very manageable and useful.

    FWIW, Scrapbook is a FireFox extension that saves selected HTML from a web page to my local disk. These local pages can be re-ordered, or prioritized even. This is very useful when I'm concerned the page's content might disappear in the future. A useful research tool!

    --
    You can't be ahead of the curve, if you're stuck in a loop.
  24. Tabs Outliner extension by Anonymous Coward · · Score: 0

    There's already a Chrome extension like that, it's called "Tabs Outliner". It's a bit quirky but it works! Too bad it can't be docked to the main window though...

    https://chrome.google.com/webstore/detail/tabs-outliner/eggkanocgddhmamlbiijnphhppkpkmkl

  25. Who needs tabs by Anonymous Coward · · Score: 0

    For more than 3 pages tabs are a pain. I use my own browser (webkit) with a drop down list.

  26. Re:"Thousands of bookmarks"? Why? by Anonymous Coward · · Score: 0

    Yo dawg, I heard a company bookmarked the entire internet for you. Its called Google I think.

  27. Re:"Thousands of bookmarks"? Why? by Anonymous Coward · · Score: 0

    There is no wrong use-case for bookmarks.

    Bookmarks are there for interesting things. Age of interest doesn't (shouldn't) come in to it. (starting to sound creepy)

    I have bookmarks of interesting sites from years ago. Articles. (here included)
    Small websites, old community sites.
    Or how about social networking profiles. You never know when Facebook might delete your profile just for existing. Poof, there goes your contact lists.
    I even use my bookmarks to store non-URL information. Emails. Addresses. Never know when Google will axe you for real-name policy bullshit they always say isn't an issue now.
    I'd store notes too, but that is just too much hassle and won't work nicely at all. Easier to just use a separate document for that. HTML document at that. Guaranteed to work everywhere and for many years, unlike the newest hit file format from Microsoft or the open source community alike! (Sometimes, dinosaurs are good.)

  28. Re:Tabs on side?? How about tabs on BOTTOM. by Anonymous Coward · · Score: 0

    Why the hell are people so up in arms about Mozilla not doing what they don't have the resources to do, and making us do them as addons? Clearly there are a lot of bugs with the native UI, and if Mozilla can't fix them quickly enough and people keep leaving for Chrome, then why should they be forced to do everything for us?

    Seriously, this attitude is rotten to the core. I understand that it's easier and less frustrating to have someone else do the work for you, but Firefox isn't Microsoft or Google - they don't have their resources. If even Google won't do it, then wake up and smell the coffee. The community has to step up and help out, not bitch and moan that Mozilla isn't doing everything for them.

    "Oh, but this should be a native feature!" is a non-argument. Everyone has a different line for what should be a native feature. Mozilla just doesn't have the time to do a billion little things like this while still maintaining and upgrading the core of Firefox. It's not like an addon will be slower; the UI is still made of the same components, you're just tweaking some CSS or what-not.

    "Oh, but extensions break all that time!" is an equally stupid argument. Of course they do! Mozilla can't be expected to maintain 100% backwards-compatibility while changing the guts of Firefox, nor to bloat up their browser any more edge and corner cases just for our most inane convenience. Someone has to step up and do the work, and maintain that work. If Mozilla says they can't do it, then we should do it, not be drama queens.

  29. Re:"Thousands of bookmarks"? Why? by Anonymous Coward · · Score: 0

    No, I'm not doing it wrong. For example, I see tech-notes and answers all the time on stackoverflow.com, so I bookmark and tag them for future reference, so I CAN forget about them.

    I don't know. Reference is one thing, but it seems like it'd be more useful to, you know, actually learn the material rather than trying to track down which of your thousands of bookmarks has the answer you're looking for.

  30. ...because right now Chrome on the desktop sucks. by Anonymous Coward · · Score: 0

    A hierarchical side tab is badly needed because right now Chrome on the desktop sucks. Badly. Like really bad.

  31. Re:Tabs on side?? How about tabs on BOTTOM. by jlv · · Score: 1

    +1 for "Classic Theme Restorer"

  32. Why use Chrome at all? by jlv · · Score: 1

    I stopped using Chrome the *second* time it just stopped working correctly, because an extension I depended upon got "updated" and thus no longer worked. I can't stand having to figure out why things aren't working correctly anymore when I haven't changed anything. As long as it's impossible to lock down the software until *I* want to update it, I'll just opt out of Chrome.

  33. Re:"Thousands of bookmarks"? Why? by Anonymous Coward · · Score: 0

    Because no one offers a "personal search pool" yet and those bookmarked locations were non-trivial to find - many of them were not found with the first round and a lot of keyword adjusting to discover (more and more keyword adjusting, as google continues to "simplify" search...). For those of us living far from the bay area, each round of searching takes a non-trivial amount of time.

  34. Re:Tabs on side?? How about tabs on BOTTOM. by markdavis · · Score: 1

    Although I agree with a lot of what you said, the issue is that the code was already there to put the tabs on bottom. They removed it for no good reason except to enforce their vision of looking exactly like Chrome. First the changes to the URL bar, then the style, then the addition of the menu button, and now removal of tab location choice. It is a sucky thing to do. If we wanted Chrome, we would use Chrome.

    If they want to remove crap and bloat and simplify the base browser (like it is SUPPOSED to be, that was the GOAL of Firefox), then made the damn "developer tools" an add-on. 99.9% of Firefox users have absolutely no need for them, so why is all that long and extremely complex code part of the native browser- making it complicated, and taking up lots of space?

  35. Re:Tabs on side?? How about tabs on BOTTOM. by Anonymous Coward · · Score: 0

    They removed it because they were updating their UI code and don't have the workforce necessary to maintain all of these UI options. I know that it's fun to pretend they're just assholes, and that they're just cloning Chrome's UI, and that they're the Devil, but honestly: tabs on the bottom is FAR less important than other things they're working on. Stop being babies. The new UI framework makes it easier to maintain such features, so if Mozilla doesn't want to maintain it themselves anymore, then you should be able to add the feature back yourself. Too hard for the Slashdot crowd? Or are all of our petty little frills so important that we want Mozilla to let the core of the browser continue rotting away instead? Developer tools are far more important than having tabs below your damn addressbar, as they let you actually figure out how to do things like place the stupid tabs under the stupid address bar. But only if you want to do something instead of cry and whine.

  36. Australis sucks by HBI · · Score: 1

    Tired of updating every few days for guaranteed regressions.

    Don't need the SJW crap.

    Fuck Firefox.

    --
    HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
    1. Re:Australis sucks by Anonymous Coward · · Score: 0

      Well there's your problem, you're living in some alternate reality. Apparently using Firefox when it's renamed Pale Moon makes you feel better about yourself, and when Pale Moon breaks shit it's still better. Oh, and nice touch with throwing SJW in there. I'm sure all the 13 year olds will flock to your cause with that. Why not bring up how Mozilla failed to make Theora the default video codec? Or how they broke Firefox by removing the status bar? Or how they're doing nothing these days except copying Chrome?

    2. Re:Australis sucks by HBI · · Score: 1

      Umm, isn't Australis the Chrome-copying interface?

      Nice astroturf for FF. Too bad no one cares, no tears for those assholes. The project is badly managed and will suffer the fate of those who are serving a niche audience. Who knows - maybe there is more of a market for a LGBT browser than I think.

      --
      HBI's Law: Frequency of calling others Nazis is directly correlated with the likelihood of the accuser being Communist.
  37. Re:"Thousands of bookmarks"? Why? by Anonymous Coward · · Score: 0

    Yeah, you are doing it wrong. Bookmarks are supposed to be used for URLs that you want to permanently store in the browser. If you're only trying to store an address temporarily, something like To-Read Sites extension is what you should be using.

    FWIW, Scrapbook is a FireFox extension that saves selected HTML from a web page to my local disk.

    You act like that's some big deal. Chrome can save entire pages too. Opera and IE can save entire pages into a single MHT file.

  38. Re:Tabs on side?? How about tabs on BOTTOM. by Anonymous Coward · · Score: 0

    Mozilla has more money than Opera does and Opera doesn't have any problems making a non-broken browser. Don't even make me bring in other browsers like Midori, which still works better than Firefox.

    If Mozilla were so hard up for cash, as you wrongly claim, then maybe they should ditch that fancy, *CUSTOM-BUILT* silicon valley building of theirs and move into a warehouse in Oakland.

    If Mozilla wants to hold on to their userbase, they need to be competitive and lose the sense of entitlement.

  39. Fuck Google to death with a sword by Anonymous Coward · · Score: 0

    I regularly have anywhere between 1,000-5,000 tabs open in my browser, as I load vast numbers of web pages daily and click on links to be loaded for offline viewing. The day the dumb fucking assholes at Google decided to remove the vertical tab feature is the day I ditched Chrome forever. Firefox is likewise a piece of shit, but I can at least see what tabs are open and switch from one to another in between occasional crashes. Most days I wish someone would gather up most programmers responsible for the WWW (as well as Lennart Pottering, just because), boil them slowly in a vat of acid, then put the video on Youtube.