Gentlemen...

I didn't mean to start a negative dialog and perhaps I should have phrased my statements in a more positive way (too many years of dealing with whinny employees, I guess...).

I think that we can all agree that BIAB does have some really good and useful things about it, as well as recognizing it's down sides.

From a practical point of view (from nearly 40 years of working with marketing) it's easy for me to read the tea leaves because I see the similarities between my involvements in purchasing software (on a very large scale in excess of multiple 6 figures) and the mathematical statistics of the field of users. Including my own user experience.

As a programmer (an often needed trait for me) I know what going back to the drawing board can be in terms of a real hassle - I'm presently converting code from java to objectiveC and I can't fault the BIAB folks for hoping to minimize their costs/time. Yet, I also know (by experience) the benefit of starting from a clean sheet of paper and I hoped to encourage that by my posting - for two reasons:
1 - So it might lead to a change that users would like and not feel they have to fight it's interface
2 - So BIAB folks could reap greater rewards from an increased volume and more positive audience

And, I suppose lastly, as a geek, I have no problem debugging software and providing feedback - I just hate to have to pay hundreds of bucks to do it and then, to have to pay for an upgrade that (hopefully) fixed the bugs. That's where I draw the line - I'm comfortable with slogging through BIAB in it's current form and will not buy any upgrades nor can I recommend it to my music students.