Re: "continuous development"
In some cases, sure. In many cases though, that's not the reason. Plenty of well-regarded projects are run that way. Linux, for example. A lot of the updates fix bugs and add features and we're usually quite happy about it. They have only three choices. They could do what they currently do, they could do a lot more testing on everything, holding back updates, or they could stop development entirely and focus all their time on a single-release perfect OS that would never need updates (I.E. the perfect example of vaporware). I think many would agree that their current approach is optimal. Continuous development, as you put it, is only a problem if it's used to disguise frequent bug releases, but you can release buggy code quite easily without needing any specific development strategy, and proof of that is available everywhere.
Biting the hand that feeds IT
