Slashdot Mirror


Places Feature Cut From Firefox 2

segphault writes "Apparently, the new bookmark and history system (called 'Places') scheduled for inclusion in Firefox 2 has been removed from the roadmap and disabled in the builds. An article at Ars Technica discusses some of the implications: 'Since Firefox 2 (and all alpha builds from here on out) will use the conventional bookmark system, those of you that have been using Firefox 2 alphas (the Gecko 1.8 branch) will have to export your bookmarks to HTML in order to preserve them. As a Firefox user and a software developer, I am personally very disappointed with the removal of this innovative feature.'" Update: 05/01 01:16 GMT by Z : Ars link updated.

12 of 394 comments (clear)

  1. Firefox has the wrong focus by Theovon · · Score: 4, Insightful

    Just like Microsoft, Firefox developers have gotten stuck on the feature-creep treadmill. Instead of fixing incessant crashes and debilitating memory leaks, they add more whiz-bang features to compete with the "enemy". Instead of adding features to make their browser more robust and responsive, they add more crap to make it bigger, slower, and buggier.

    Firefox is no longer about doing the right thing. It's now all about one-upping Microsoft at their own stupid game, and the users are suffering for it. Open Source developers, apparently, are no more ammune to this competition attitude than the proprietary vendors. There is no longer anything special about Firefox. What's more, they suffer from the syndrome many open source projects suffer from, which is that they prefer to work on the "interesting" bits, rather than spending time adding some polish to make things work WELL.

    1. Re:Firefox has the wrong focus by Xelrach · · Score: 5, Insightful

      Doesn't the fact that "Places" was delayed show that they _are_ focused on polish?

  2. yes, but by fuentes · · Score: 3, Insightful

    Disappointing, yes, but this is what makes excellence in software. They recognized the problems, realized the time it would take to fix, and decided on a "better safe than sorry" approach. This will make the eventual release of "places" that much better!

  3. Re:Differentiation by CCFreak2K · · Score: 3, Insightful

    I don't want to start a flame war, but maybe there's more going on under the hood than at first glance. For example, imagine a Windows 2000 Professional box and a Windows XP Professional box with the regular Windows Classic theme. They both look a little different, and they both act pretty much the same, but they're quite different.

    Maybe a better example for the /. crowd would have been Linux and *BSD with X/KDE one each, heh.

    --
    "Beware of he who would deny you access to information, for in his heart he dreams himself your master."
  4. Why do the 2.0 release? by mccoma · · Score: 4, Insightful

    I guess I am a little confused what the rush is. Can't they just hold the release until they get this feature correct? It is not like they are selling a product and need the churn to make revenue.

  5. Re:Parent isn't shouldn't be marked redundant! by KingJoshi · · Score: 4, Insightful

    Because marking a post 'redundant' is a punishment. That's the system that we have. A person trying to help out the community by providing a proper link shouldn't be punished and their comment doesn't need cleaning up. We do have to assume the intentions of people and that's why this post shouldn't be marked redundant (at the time they starting typing, the other 'redundant' post didn't exist). If it's rated high when a previous post does the job, then you can rate it 'overrated'. That follows the spirit of the rules, IMO.

    --
    In times like these, it is helpful to remember that there have always been times like these. - Paul Harvey
  6. Let me start by quoting... by Biomechanical · · Score: 5, Insightful

    ...My earlier comment on Digg when this story showed up there.

    Personally I couldn't give two shits about _any_ browser getting "new and exciting!!!!" features right at the moment, and my reason is very simple,

    They all fail at what they are supposed to do, first and foremost. Some fail utterly, and other fail a little bit, but they all _fail_.

    There is not a single browser available for download at the moment that _fully_ supports the web standards laid down by the W3C, http://w3.org/ and developers who are working on Safari, Konqueror, Mozilla Firefox and Seamonkey, IE, Opera, Camino, and so on, all need to take a step back from their computers and say,

    "Hey, how come we're adding new features to a program that isn't even standards-compliant?"

    The continual lack of support for even the full subset of CSS 1 and 2.1 makes designing pages based on XHTML and CSS a frickin' pain in the arse.

    If there was one browser, even just one, that was cross-platform and fully supported even just HTML, XHTML, CSS 1 and 2.1 (maybe even parts of 3), and was extensible to support such things as SVG and XVRML, then I would be using it in a damn shot, and then I'd _know_ that when a page failed to render properly, _I_ screwed up, not a bug in the browser.

    Stop adding features guys, just follow the damn standards.

    All I want, and I'm betting so do a great deal of other people who work with the web, is a browser that follows the standards for HTML, XHTML, CSS 1 & 2 (maybe even 3), Javascript, and DOM.

    Extra features are nice, yes, but the top priority should be putting out a browser that follows the standards, first and foremost.

    What good are extensions and themes and fancy bookmarking tools if the core program for seeing information on the web cannot render pages which have been correctly created?

    --
    His name is Robert Paulsen...
  7. FIX THE DAMN MEMORY LEAKS ALREADY by ameline · · Score: 3, Insightful

    Sorry for shouting, but I'd be happy if they did *nothing* but fix the memory leaks.

    Memory leaks are unforgivable.

    --
    Ian Ameline
  8. Re:Differentiation by et764 · · Score: 4, Insightful
    The close button'll be on the tabs, but that seems about the only user-visible improvement.

    In my opinion that's not really an improvement. I prefer having the close button on the side like it is now, because that way it's always in the same place, instead of having to find which tab is active and then home in on a new place for the close button each time I have to close a tab.

  9. MOD PARENT UP by Trogre · · Score: 5, Insightful

    Putting close buttons in individual tabs is nothing but evil, wrong and stupid.

    One mis-click on a tab (which is very common when managing a dozen or so tabs) and you've just closed an important page with no confirmation dialog.

    See http://bugzilla.gnome.org/show_bug.cgi?id=335453 for the current gnome-terminal fiasco.

    Just don't do it.

    --
    "Nine times out of ten, starting a fire is not the best way to solve the problem." - my wife
  10. Re:Differentiation by number11 · · Score: 4, Insightful

    in order to convince users that updates are worthwhile you need visible differentiation.

    I hate visible differentiation. It's disruptive. Especially change for the sake of change, I can live with it if it actually improves something. Once I've figured out how to do stuff, where the menus are, what the shortcuts are, maybe customize the toolbar a little to get the functions I actually use up there, I resent it when the developers mess with it just to say "hey, look at what we can do, aren't we cool!". Then I spend a few hours figuring out how to put as much as possible back to the arrangement it was in before.

    Maybe I'm an anomaly. Or just an old fart. I rarely change the GUI from the default unless it's to make some feature easier to use. And if I do make those changes, I want them to carry over to the upgraded version. The only software I use skins with is where the default eyesore verges on unusable (for some reason, media players tend to fall into this camp). Just give me the improvements under the hood, please.

  11. Re:Bad URL by mabinogi · · Score: 5, Insightful

    if I have to stare at a blank page while my status bar says "waiting for google-analytics.com" then either I'm going to block google-analytics.com, or I'm just going to get fed up and stop visiting your site.

    It really bugs me just how often I have to sit and wait for my browser to contact 5 different ad and stat sites when viewing some web sites - slashdot being one of the big offenders.

    I have no problem with you providing (tasteful and discreet) ads, I have no problem with you collecting stats. I do have a problem with having to wait for that to happen, when I could be reading your site.

    --
    Advanced users are users too!