I suppose I should clarify by "latest" that I mean a version of a piece of software that is actively supported and has all the security patches. Like it or not,

I suppose I should clarify by "latest" that I mean a version of a piece of software that is actively supported and has all the security patches. Like it or not, the ecosystem is currently built around the assumption that you do want to have this, that nobody should still be running e.g. Firefox 34. The question is what the best way of shipping it is. The conversation in the two posts you replied to isn't about whether you always want to be on the bleeding edge all the time, it's about whether it makes sense to have a centralized repository that contains the latest version on some supported channel, which isn't necessarily the same thing as the latest -nightly. I take the position that it is; that shipping a (potentially) different version of a library with every application is a bad approach which is often less secure and harder to maintain.