Additional summary. "Not everyone wants automatic updates, so you'll still be able to do it the old way if you choose."

This is what I like about Mozilla, choice. Thank you to the devs that keep user choice in mind.

Based on a lot of feedback we're also going to only start the service when it is doing an update to ensure no overhead.

Why would you do it any other way? Laziness?

Why should a user program require an updater that needs to run with the root privileges? If it were on a #nix box that is locked down comparably to Windows/UAC, Firefox would've been sitting in ~/bin together with all other stuff that the user installs for himself. Windows remains the only mainstream OS that does not even have a notion of user-installed software and mandates (through its guidelines) that all software to be installed into %ProgramFiles%. There is an UAC, but there is no %UserProgramFiles%. This is truly idiotic, if you pardon my late night French, but not a bit surprising.

What is a 'user program'?

If you're on a Linux machine the vast majority of people are going to use a package manager to install their software. It ends up in /usr not /home.

I don't get your argument. Sure, you ~can~ install to ~/bin (and I'd guess you could change the FF install path to something outside of UAC protection/virtual folder redirection, maybe even now), but the majority doesn't. Not on Windows, not on Linux. Or are you going to tell me that the gazillion Ubuntu users install FF to ~/bin? How are they updating their packages?

Right.. With a process that runs as root.

Not true; From Windows 7, Windows supports both per-machine and per-user "installation contexts" with separate "Program Files" directories:

http://msdn.microsoft.com/en-us/library/dd765197%28v=VS.85%2...

(see "ProgramFilesFolder" section)

It's definitely much easier to leave your service going at all times. Google and Apple both go this route, despite the waste of resources implied.

If done right, it shouldn't be that much of a performance drain, and the benefits would outweigh that.

What benefits?

Why use a Windows service instead of installing in the user's %APPDATA% directory like Chrome? Admittedly, there is some wasted disk space if a Windows PC is shared by multiple users, who each install Firefox. But I imagine most Windows PC only have one user account.

From the article:

There are several ways to tackle this issue. For example, some browsers that offer silent software updates will install into the user's application data folder and hence do not have this problem. We could do the same, but we chose not to because it can be an administrative headache for some people who manage updates themselves and have to maintain an installation for every user.

Sure, but that's a lousy excuse.

It is an administrative headache - just as they noted - for some people. The vast majority runs Windows with a single user account. Moreover, installing into %AppData is equivalent to installing into ~/bin - and this is exactly where user's programs should go.

In other words, they have it backwards. They should be defaulting to %AppData with an in-process update mechanism, and optionally let it be installed into an admin-controlled directory, in which case fallback to the service-based updates.

No, apps go into Program files.

Why?

Because you're used to have the choice of installing 'for me' or 'for all users' for aeons now on a Windows system.

Because even my tiny deployments are better and safer if I can make sure that FF is updated for every user of my machines, instead of hoping that they'll get an update next time they browse Facebook.

Because it's wasteful to install the very same software to different places. Yes, storage is cheap on modern hardware. No, not everyone uses FF on modern hardware.

Profiles belong to the user. The application belongs - in a Windows world, in a Linux world - to the system / administrator.

Love the mozilla guys for keeping the expectations intact. Re: "Program Files": Maybe ProgramData would be a decent place to drop updates. Program Files is supposed to be readonly, ProgramData is afaik the place designated for system-wide application data.

> the choice of installing 'for me'

Right, and this puts program files into a system directory, but the Start Menu shortcuts into the user's profile. That's not exactly "for me", isn't it?

> Profiles belong to the user. The application belongs - in a Windows world, in a Linux world - to the system / administrator.

That's in a Linux world that is modeled after the Windows one. In a traditional #nix world there are system binaries and there are user binaries. If the user needs something that is not readily available on the box, or if he needs a specific version or whatever, he can install it into ~/bin. Point being, that on Windows this is not even an option. There is no standard location to put user's personal program files into.

Google Chrome offers a version for enterprise, where Chrome is installed into the Program Files directory.