Hi all, just thinking aloud about things that have been written here.
I would like to point out / remind that there are some very strong examples of projects / teams that are very well organized, working on daily basis and delivering amazing results. Yes, I’m talking about these amazing guys from A32NX, WorkingTitle, all the independent community content creators concentrated on flightsim.to, many many others to mention…
They are able to continue in their development despite of having direct support from MS/ASOBO or not, they are very flexible in terms of adapting their work with literaly every update of the ASOBO’s codebase. And they are rather keeping fixing things than sustainly “complaining”, providing to US, MSFS users, the content that is really valuable and in the final consequence it helps to make the whole platform better and more popular. They are simply willing to take a risk and work in these unstable “combat” conditions.
I’m of course aware of big difference between these community projects / volunteers based development who are doing things for free and for fun and a real payware creators who is doing thieir stuff not only for fun but also for profitt. I’m almost sure that ASOBO/MS is aware of both these groups and their importance to their product success. I’m mentioning these community creators mainly because there are currently really large amount of them, statistically very important amount of them. Several times more AT THE START of the the platform lifecycle than at the start of any other sim before. That’s very strong proof of that this works despite of problems that needs to be solved. An this all is happening just two months(!) from the official launch, just to put things in context.
Yes, there are bugs, there are also unfinished things that need to be fixed, tuned and finished, early growing pains of unexperienced developer, etc. But we all are continuously learning from our mistakes, changing our minds and processes, improving things, trying to listen to communities, iterating…
TBH I thing that one of biggest problems of “present days” is that the world is “spinning too fast”. Almost everything is one-click away from our comfortable chair, a lot of people I know (especially younger people) really need everything “now” and if they don’t have itnow, they get quick nervous and angry, like there is no tomorrow. I believe that ASOBO is very aware of this trying to provide us things quickly (in 14 days iterations), but there is also a downside of this - bugs, big rush, not enough time to do some exhaustive complex testing, … In the past it wasn’t so easy for us to point out issues MINUTES from the release. No it is, unfortunatelly for the developers. 
I’m just thinking about the FSX era. There was the initial release (with issues, bugs, unfinished things), then SP1, then SP2 nad it was all. It was easier for add-on creators to develop their things on stable platform, with just these two major updates. But nowadays this approach is simply not applicable, because people are used getting things so quickly. I believe that majority here checks for some updates every single day(!) and expecting at least some new information. 10 years ago it wasn’t so common behavior…
So finally, it’s obvious that there is a lot of things that need to be done on ASOBO side. And sometimes it might be very painful process for all. But there are things that we simply need to consider, not to be overseen, for example that things are continuosly changing and thing just need some time to be stabilised, finished and ready.