My argument is that consumers get features sooner, so thats good.
Assuming that the consumers want the new features. It depends on the user, but there are lots for whom new features are problematic. They can introduce costs and uncertainty in the short term, and so have to be planned for. This takes time. If new feature come too frequently, it becomes too expensive or unwieldy to use the software.
The other side to it is that if an update breaks for you, then just dont update.
That's not how rapid release works. FF hasn't completely implemented it yet, but ultimately you will not even know that an update is coming or be asked if you want it. It will just happen in the background. It'll probably remain possible to turn off updating completely, but eventually that will lead to a different problems as more and more plugins and server software assume that your browser is always updated.
Why do people feel the need to be on the latest version and then complain about it. If it isn't what you want, dont do it...
Indeed! However once FF is fully rapid-release, the only reasonable way of not updating is to not use FF.