This criticism is based on the assumption that all updates are created equal. But they aren't. One week, the update could be a relatively minor bug fix. The ne

This criticism is based on the assumption that all updates are created equal. But they aren't. One week, the update could be a relatively minor bug fix. The next week, a major feature upgrade that's been in the pipeline for months. You also remove the ambiguity of "Is this worth pushing out? When should I push this out? Should I do some more fixes or push this one out first?". You got fixes, push them out in the next update. Your criticism also assumes a small team. If you have a large enough team where you can split them into new feature development and current bug fixing, they're going to work at different rates and be ready at different times. If instead your entire team just works on "the product", then there is no effective difference between fixing issues and creating functionality.