On second thought rjf, perhaps I have been to harsh. if you have reported more bugs than VB, please say so. That is something that we all can appreciate and and even if you have reported less, reporting any is a good thing, as is fixing any bug a good thing compared to fixing none, but it would be better to keep the bug backlog down to the ones that no one knows how to fix.
It is hard to understand how a 25 year old product can have the many bugs that VB reports but obviously it does and that suggests that VB is providing a good service and I might add doing it for free, so he deserves credit for his many contributions, not criticism.
"And just because someone ADVERTISES that the bug backlog has been cleaned up for the next version, does not mean it has been done." True and even more reason why the reporting and action taken to correct bugs should be public knowledge. That way the companies that are honest get credit for their honesty.
"Even if it has been done, perhaps many new bugs have been introduced." Again true but that has nothing to do with reporting bugs. Are you trying to change the subject??? I believe I read somewhere that some people were advised to use that tactic. A developer that I greatly respect has written that "writing near-defect-free code is possible for new programs" so I would assume that not many new bugs should be introduced by the new code that is written. Regardless, I will buy a new version because it is less buggy and not because it analyzes stock market trends or similiarly produces astrology predictions or weather forecasts. The cas world has expanded greatly in the last few years and now is the time to consolidate those gains with quality improvements.