I disagree about expectations too. Users have a great deal of built in expectations for chrome after having dealt with other browsers for years.
If firefox and chrome switched their update systems, the story we would be hearing would be "I tried chrome and i hated it.", and they probably wouldn't even bother to tell us why (the nagging update system.)
Okay then.
Previously, when I went to a new browser experience, I generally went to a new browser.
There was Mosaic. Then Netscape. Then Galeon. Then Konqueror. Then Mozilla. Then Firefox.
Galeon was probably the most jarring of the bunch. It started as a highly power-user friendly advanced (for the time) browser. Then the GNOME project "adopted" it as its default browser ... and instilled it with "simple user" disease. Many features were ripped out, and much of the userbase left in disgust (there are a few postings by Jon Corbet and other at LWN.net I recall). Eventually it was replaced by Epiphany, a pale shadow of the original.
Life would have been better if the rebranding had happened first.
And we'll note that Mozilla has already gone this route several times: Netscape -> Mozilla -> Phoenix -> Firefox. They should have taken this as a new fork as well.
That said, with the except of one FF push on OSX that broke Netflix for a few days I've been pleased with the changes. Safari's constant memory leaks drove me nuts, FF leaking memory wasn't as bad but certainly annoyed. They've solved that problem for my usage and having suffered with Chrome "dev tools" I continue to use FF and Firebug for front-end work when need be.
Have you tried Vimperator for Firefox?
Modal, action happens on a status line at the bottom of the screen (allowing you to minimize navigation elements -- no navigation, menu, or toolbars). To open a new tab, type "t <pattern><tab>", where "pattern" is either part of a URL or the title of a page or bookmark. To open Hacker News, for example, I generally type "t hack<tab>". If there are multiple matches, they appear as a list of items you can tab through (or which shrinks as you type additional characters for greater specificity). I like it.
Chrome's navigation is similar, but not quite as slick.
So, if that's true and people stuck with Firefox, you'd have to maintain Firefox between the snapshot releases of Frequentfox. You'd have to push an update at least every time you fix a security issue, which can be pretty often. So you'd still need to figure out a good user experience for dealing with frequent updates. Fortunately, that's a solved problem, and the user doesn't even need to notice you've updated their software.
Of course as you add features and modify/improve the user interface in Frequentfox, your Firefox snapshots will be different enough that you'd still end up alienating users, so you can't go crazy developing Frequentfox, either.
I'm voting for frequent push updates, transparent if they don't change anything significant, and with a gentle introduction to the changes if they do. Big changes should be rare, maybe explain the motivation behind them to the user, and ideally make them option. Despite all the rage, I think the user interface changes from Firefox 3 to trunk weren't all that jarring; significant tweaks more than fundamental reworkings of the UI, the awesome bar is a great example.
[1] Edit: I think this is what you call a "second-order decision", a term I just learned, e.g. http://thinking-marketing.blogspot.de/2009/11/second-order-d...
How to reach out to new users while keeping your existing users happy is one of the oldest and biggest problems in software development. There's no perfect solution, but I like the suggestion of creating a new product name for the new thing. That can sometimes get you into trouble too, as you end up competing with yourself, Microsoft-style, or get users who are confused about which version they should use. But it might be the least bad option.
That's a fair point, but also true is "don't let your product stagnate by keeping it familiar and unchanging". People get bored with similarity and want new shiny things.
There is something to be said for too much change, and something to be said for too much sameness.
I disagree. Users want something new if their current software isn't meeting their needs for whatever reason. But if it is meeting their needs and they know how to use it, then keeping that software the same isn't "stagnation", it's stability.
Whenever I hear users ask for change it's because there's a feature they wish they had or a bug that's annoying them. I've never heard anybody ask for change just for the sake of change, or complain that software was boring because it didn't change.
For games I guess it might make sense to keep changing things up just to keep them fresh, but for productivity software I think "boring, predictable, and functional" is the ideal state. Productivity software isn't supposed to be entertaining, it's supposed to be useful.
What if their need is for something new and shiny?
Have you never heard people say they tried Chrome because it was new and shiny (even the word implies shininess)? Or how about how people want to buy the latest iPad or iPhone, it isn't because the old one isn't "meeting their needs" in some boring sense. They want something new and different.
> Whenever I hear users ask for change it's because there's a feature they wish they had or a bug that's annoying them
That is a very simplistic view of users. Users are human beings - they want conflicting things, both for things to work and be predictable, and for things to be new and interesting.
The right tradeoff is the hard part, not absolute black-and-white principles of "users never want change" or "users always want something new and shiny".
There are some large businesses out there who run the same software foundation for a decade or more, not least because just evaluating a new version of something critical like an operating system or web browser can be a huge exercise if you're running hundreds of in-house tools on top of them.
While I think it's unrealistic to expect an OSS browser to provide ongoing support for that long, if Mozilla want their product to be taken seriously by enterprise customers then I suspect they're going to need a lot more than a year of security fixes and a lot more than 6-12 weeks of overlap when they want to force an upgrade. It would be interesting to know whether in reality they have gained much from offering the first ESR (which is already coming to end-of-life) in terms of acceptance of the rapid release schedule in larger organisations. Maybe there is a certain size of organisation that is flexible enough to take advantage of a yearly update but can't take the overheads of stuff breaking every six weeks.
For software like that, a web browser is not the right platform. Web browsers view a shared space which constantly changes and gets updated with new APIs and deprecated APIs and so forth.
If you want decade-long stability, use a platform that is tightly controlled and gives guarantees of backwards compatibility, for example Java or .NET.
You seem to be confusing the Internet with corporate intranets. Browsers installed in these kinds of organisations, and the tools they want to use long-term, tend to be based around the latter. Having stability is far more important than being able to use HTML5 local storage and add drop shadows to your titles in CSS. There is a reason that, despite the endless moaning of web developers, many places are still running IE6.
If you want decade-long stability, use a platform that is tightly controlled and gives guarantees of backwards compatibility
They are. Unchanged is about as controlled and backward compatible as you can get!
Anyone who wants to get a replacement browser into these environments for the long term needs to understand that. Anyone who wants to make cloud-based solutions that seek to displace well-established in-house tools needs to understand that, too. It sucks if you want to use the shiny new possibilities of bleeding edge web technology, but the grown-ups aren't interested in an anatomical measuring contest between browser makers about who can be first to ship the next non-standardised, subject-to-change-at-any-time, bug-ridden-anyway feature.
I think Microsoft does understand this, and that's why they are still dominant in large organisations despite appearing to be behind the curve. I think Google have figured it out as well, but when they stopped supporting IE6 in their web apps, it wasn't because they had successfully forced everyone to upgrade, it's because they realised that they never would.
Since there are open source browsers, you can just save a very old version of them for intranet apps, if you must. But you can't expect a modern browser to still run your old intranet apps, you will need both a legacy browser and a modern one.
The ESR fits somewhere in the middle. It won't run 10 year-old apps, but it will update very slowly so your IT department does not need to constantly verify it (only once a year). Again, for 10-year-old apps, that won't work - you just need to install a 10-year old browser. If you just run it on intranet apps, security isn't a concern so that's fine.
>While I think it's unrealistic to expect an OSS browser to provide ongoing support for that long
According the the author, Chrome isn't the solution.
Firefox on the other hand... sigh. I really liked that browser, but the updates, and the broken plugins, and the shit memory management, and the developers' heads up their shitty asses denying their shit memory management, and did I mention the enormous memory usage on OSX? Chrome essentially has the same uptime as my laptop, ie months. Firefox required daily restarts with the same browsing patterns. Plus they regularly corrupt the backing file that holds the sites you had open in your browser, so before restarting the browser to get ram back, it's a best practice to copy the location of each and every open tab to a text file.
We got my gf's laptop 8 gigs of ram to accomodate ff and I'm working on talking her into chrome. A browser written by people who know how to use free(3). Plus the updates don't hork random stuff. Plus on the rare occasions I've restarted the browser it has never broken the backing store holding the open tabs.
We've had a project called MemShrink running for about a year and it has been making steady progress. and that progress has been shipping to users.
The current Aurora channel release even has a fix for most add-on bad behavior.
Firefox actually stacks up really well in memory usage (even in third party tests).
(I work for Mozilla but was not involved in MemShrink. Also, I wrote this on my phone, so I hope there are no embarrassing misspellings. )
It was so bad that I had to close firefox when I wanted to do anything else. If I played a full screen game it would work great for about half an hour the suddenly it'd chug along at 10fps. Without fail the issue was Firefox deciding to consume 90% CPU. And again this is without installing a single add-on ever.
It may be better today. I don't know. I don't care. I switched to Chrome and haven't looked back since.
And then years later they have the "MemShrink project". Which basically was admitting that they were spouting bullshit about it being addons for years.
State recovery is quite good for the most part, even if memory use is somewhat pants.
This isn't to say Chrome doesn't have its own memory or performance problems. GMail for example will eat up to 1GB of memory eventually before I notice I'm low. I have to actually close the tab (reloading doesn't fix it) and re-open it. It's "only" using 500MB right now...
Any organization that can live in denial for years and years about the core issue with their product is going to die. Mozilla is tightly connected to the web developer community, but has a complete disconnect from the problems facing its actual users. When Firefox shipped, it was a great, light-weight alternative to Mozilla. From my point of view as a user, I haven't seen any substantial improvements since 1.0 shipped in 2004 -- spell check is nice, and given how often it crashes, restoring tabs when the browser is opened is nice -- but that's all. Otherwise, if not for security issues and web site compatibility issues, I'd be on Firefox 1.0 (which worked fine on sub-GHz machines).
Aside from that, virtually all development effort has been aimed at making a better IDE for web developers. I guess that benefits me since, ultimately, I can visit nicer web sites in Chrome.
Which is expected, because why would you stay if you were really bothered?
Comments from an active user, though... I've stuck with Firefox out of habit probably more than anything else, but now most of the things people (including me) were complaining about are already gone -- as of the last update, Firefox with -- sheesh, I guess I have about 100 tabs in 2 windows -- takes up under 500MB after using it all day, and in the morning it starts in a few seconds (they don't force-reload all your open tabs on startup anymore, just the active ones and I think text from the others is cached locally).
Chrome becomes unusable if I try to use it like a to-do list like this, for UI as well as memory reasons; not that I could say easily how much memory Chrome is using at the moment, with 20 tabs; the separate processes defeats seeing that easily, alas (there must a simple way to check, but I haven't tried).
It's quite stable, and even when it was still crashier (last year?) it's been years since I've actually lost my tabs after a crash; they've always been auto-recovered (and it has that nice prompt to let me close the ones I think may be causing trouble before relaunching).
Given different usage patterns, etc., I have no idea if people trying the actual, current FF will want to go back -- but for anyone who left more than a few months ago (especially if you left due to memory footprint) I'd suggest trying it again sometime.
[And I like the more frequent releases, personally -- I always hated the slow release cycle, and feel like they're starting to get into the swing of it now -- but I obviously don't speak for the crowd on this one...]
The equivalents on Chrome are simply not good enough. I don't know if this is an issue with all Chrome extensions, but Wet Banana / Scrollbar Anywhere on it seem to be running in a low priority and thus have sub-par performance. Scrolling is choppy and doesn't always even initiate, depending on where on the page I right-clicked.
And things have improved quite a bit more since FF7.
It leaks a lot when it's using a tiny amount of memory, and it leaks hardly at all when it's using a large amount of memory?
Sorry, but that's totally nuts.
Mozilla have been claiming "we've solved the memory leak problem" about as long as Microsoft have been claiming "we've solved the virus/security problem", or so it seems. With about the same level of credibility.
I just finished entering a comment above suggesting people should give it another try; I have 100 or so tabs open and 500MB footprint after using it all day, with version 13 (I just stick with the release update channel) in win7.
In my experience they've very clearly fixed whatever the main memory issue was that affected my experience -- but not yours. Though -- the windows versions may get a bit more testing....
I'm running Firefox 15 / Iceweasel 10 on Ubuntu and Debian respectively, watching VIRT (total virtual memory size). Currently sitting at 2.3 GB, FML.
There's a utility called 'pmap' that you can use to display the memory mapped files and subtract it from the total etc.
Finding out how much memory a program is using is surprisingly tricky to compute. Good luck.
(Futhermore, in my personal experience, Firefox has been using less and less memory.)
If you meant your sequence to represent performance, maybe that's what's happening, but then I think they should stop saying "now 1/1024 faster than before" as if it's a reason to upgrade.
Also, I don't see Mozilla claiming memory usage follows a curve like 1/x. In fact, I don't seem them claiming anything about long term memory usage other than "it's decreasing", which is true, and can be true without implying that the memory usage will eventually be 0.
(Btw, I don't think Mozilla have ever said something as frivolous as "1/1024 faster".)
I'm pretty sure you're talking about an earlier version of Firefox -- I agree, there were problems there, but things have gotten much better with the latest versions. I run Firefox Aurora (which is kinda equivalent to Chrome's dev channel) and I haven't seen anything breaking yet.
I've also used Chrome [dev] for a while and while it was pretty good, it also decided to declare that "my user profile was corrupt" after every few days. Not fun. Plus, it could hardly handle 50+ tabs, but I guess that is due to the way the Chromium sandbox and tab threading model works (and the Atom processor in my netbook.)
tl;dr: I run Firefox Aurora (with 200+ tabs) on a netbook with 1 gig of RAM. Where's that memory problem you were talking about?
if you don't use addons, the memory management in Firefox is pretty good - actually measure it competitively against Chrome sometime
If I have more than a handful of tabs open in Chrome then Chrome starts using significantly more than a GB of RAM (in total, across all the separate Chrome processes), while I've currently got a Firefox session that has been open for more than a week, with 30+ tabs, and is using just under 1 GB.
Even so, with many tabs open, my computer hits swap far more under Chrome than Firefox.
Edit: Ah, yep, answered my own question: about:memory works in Chrome too. Using that, I've got Chrome at 360 MB with 5 tabs and 2 extensions, while Firefox is at 900 with 30+ loaded tabs and ~20 extensions.
With Firefox, you have to restart Firefox. All tabs run in the same process, and memory is generally not released back to the OS when someone just calls free() or delete.
Not to mention more headaches for web developers as yet another browser shows up with its own bugs, differing support for standards like HTML5 and CSS3 etc.
When Chrome came out, it was a new product; users had no expectations of "what Chrome is." So Google could do with it essentially whatever they wanted.
Firefox was in a completely different position. When Mozilla moved Firefox to rapid release, the product branded "Firefox" had been in users' hands for seven years -- nine if you count pre-1.0 versions. Over that time, users' expectations of what a product branded "Firefox" was settled into a particular place.
Rapid release was painful because it broke those expectations. Suddenly Firefox didn't behave like people expected a product labeled "Firefox" to behave anymore. It's like opening a bottle labeled "Coke" and having orange juice pour out. "But orange juice is better for you!" Yeah, but that's still not what I expect to get when I open a Coke bottle.
There's a simple way Mozilla could have avoided this: just call the rapid-release product something else. Create a new brand, and put it on a version of the browser that receives updates every six weeks. Call it Fastfox or Frequentfox or really anything other than Firefox. Then encourage users to start moving from Firefox to the new hotness. Make the new product compatible with Firefox extensions, but don't do the version-number compatibility check that Firefox does, so users aren't constantly being prompted to update working addons.
(Yes, both products are the same code under the hood. That doesn't matter. The important thing is that you communicate to users that this is a thing that is something other than Firefox, which resets their expectations.)
Eventually you'd have most users on the new product, since that's where the cool new features that get users excited would be showing up. Curmudgeons and enterprises would stay with boring old Firefox, but that's OK, because you make "Firefox" just a periodic snapshot of Frequentfox development. "Firefox" becomes a legacy brand, maintained for those who care about it. But the new brand is clearly established as the new hotness.
This lets you move your users without violating their expectations. They expect the new product to behave differently, because it's a new product. It's got a different name and everything!
Violent changes in direction for an established product, on the other hand, always tick off users, because they do violence to those users' expectations of what that product is.
It's better to send your well-loved legacy brand gracefully off into the sunset, in other words, than to try and shock new life into it with electric paddles.