Paul P

azslow3
But if we take one practical example.... MIDI FX in Sonar. Implemented with problems and it looks like with some bugs, at least before 2003. Still there, unchanged, 2016

And I'm sure it could be redone from the ground up and not have any bugs at all.  It's not like a mission to Mars.
 

and no-one said how big the iterations might be anyway

pwalpwal
and let's not forget, it's not the devs or the end-users who decides which bugs get fixed ;-)

So who is it?

The suits.

ChristopherM
The suits.

Going to be tough to find a person wearing a suit at Cakewalk :)

LOL!
The suits. too funny!
Good luck finding them.

Not sure how many clients I'd still have if I took that as a professional leitmotif.

I am inclined to agree with Azslow's take on the matter rather than the Ruby on Rails author.
Bugs may be inevitable but never allow complacency regarding their existence to creep into your work ethic.
Errors in performing a piece of music live (or otherwise) are inevitable.
Is any serious musician going to say 'Don't worry about it and by the way I don't want to hear bad reviews about it either' ?

One takeaway from the article is that not all bugs need to be fixed in order to keep selling the software. The other is that it is easier to fix bugs if the effort to constantly deliver more features is subordinated to making the features work as designed. The clear implication is that the users are demanding buggy software as an unavoidable result of demanding more and newer features, and paying the price for new features by having them not work as described. So the software buyers are clearly the ones at fault here. The suits and coders are just giving them what they want at a price they can afford. 

Kylotan
"Man who makes money by writing software wants you to stop complaining that it isn't good enough".
 
Excuses.

 

subtlearts
Disagree. Man who has a long track record writing useful software, running successful software companies, and writing influential bestselling books about software and business, and arguably understands these things as profoundly as anyone, explains his viewpoint - backed by all of that experience - of how software developers and companies (at least those likely to stay in business) view the subject. You think he's whining, so we should believe you? Riiiiiight. 

Ah Mr Ruby on Rails. I'm sure all their customers were thinking just that when this happened

Andrew Rossa [Cakewalk]

pwalpwal
and let's not forget, it's not the devs or the end-users who decides which bugs get fixed ;-)

So who is it?

I ask myself this question, too. This extract from the Newburyport e-zine:
 
Fixed issues where:
...
* Clean Audio Folders could hang when scanning multiple drives