Sorry, but I feel I must champion here for the developers.... This isn't a rant, but I want you all to understand the complexities of designing an addon. Sometimes, it goes much further beyond simply selling an aircraft model. Let me explain.
1) Developers have families too. Often times, when things are in a crunch or products aren't selling particularly well, a cash flow is a needed boost to continue development. This often happens near the end of a development cycle where little bugs take up a considerable amount of time. Imagine if you had to feed your family, the funds are running low and you STILL have yet more work to do on your product. For many people, the answer is simple. Release the thing and fix the issues as patches.
2) Development companies for MSFS are generally not larger than a handful of people at best. Most tend to be anywhere from 2-3 people leading the charge.
3) Some companies are naturally very scared of beta testers. Why? People like Robert Ferguson, who would be as willing to steal your product and give it to everyone on the planet. Competition, design stealing and other issues also crop up. It can be a major leap of faith for developers to bring in beta testers.
4) Beta testers are not perfect too. I have seen a great many beta tests run into several problems... For starters, it is common for a beta test to start off very well. Often times it seems like towards the end of development, the beta testers dissappear. Perhaps they have other things that are more important, such is life.
Also, often beta testers simply miss the most obvious stuff while digging for other issues, either given by the designer or their own quest as squashing bugs. I have seen many beta tests miss VERY obvious things only to be digging for the wrong thing in the first place.
5) Developers AND beta testers are people too. We are all infallable and make mistakes. It happens.
6) Other projects or time consumers play a big part in developing a product. I actually know of a few developers who are so in depth in other projects soaking up their time, sometimes they forget or simply miss the important ones in a released one. Perhaps they are trying to fix issues from old software?
Actually, I could list a lot more. My point is, please stop beating up the beta testers and developers as a first response. I make some exceptions to this, only because there are indeed development teams who maliciously or regularly do this. If however they do issue patches and do respond to support in a well mannered way and attempt to fix issues, lets stop beating them up.
This is the price we often pay when we don't wait on a product and get it when it is first released. If everything was perfect, the turn "patch" or "service pack" would not be part of our everyday geek talk.