Do you have to build one--or just pay for one--to be angry when it breaks? Of course not. The question, is at what or at whom? Naturally, you could blame the misfortune, the fact that things get old, etc. It isquite another, which is the case here, is to raise the accusatory finger at someone without a slightest reason.
You may have rightfully disliked my question, but thethrust of it was correct: before you curse MS (or another manufacturer), one has tohave at least a vague idea about the issues involved.
One could develop a notion that, after a century of building autos it's time for the price to be in the hundreds of dollars and, G-d darn it, the only reason we pay tens of thousands instead is because "they" just overcharge us. Pretty stupid, isn't it? Well, it is not more correct or more smart with regard to software: people that demonstrate the absence of basic understanding of software design and project management ridicule or accuse MS that is a conglomeration of the best talent on the planet.
Oh, sorry. I only make a (damned good) living designing and writing software, so I guess I don't understand it. However, my customers would disagree with that vehemently. Sure, bugs happen. Unintended consequences happen. I do have more than a vague idea of development. But my post was in response to your saying that unless one has some idea of the process, one should just pay up and not complain (is that an adequate paraphrase of your question?). That's a damned silly claim, no matter what you think. If I had that attitude I would expect to be out of business within days.