Asobo sais this
So… if your Community airport does not work it is that title’s performance and not the performance on the whole simulator. That is what is sais.
I download lots of packages, I have 20-30 installed, tried 30-50… When it does not work or when it does not add anything useful I remove it. I’m not an FPS-freak so I’m not sure about performance, but I’ve only had issues with 2 packages sofar. One terrain package (an airport in Chili) gave scenery distortions and a silly airport start position, the other one (a sailplane) freezed the game a few times. I don’t use liveries, but liveries can only slow down the game when you are outside your airplane looking at it. Faulty textures could (in theory) affect the game, but only if they are visible… I think the improvement you have should be traced back to a proper cause. Not some vague notion “they are bad programmers”
The Community folder (in general) does not crash your game.One web page can crash your browser, but you say like "the internet crashed my browser so I don’t use the internet anymore.
I have some experience making addins for myself, I’m not the best programmer in the world either, but i NEVER crashed anything an trust me, I tried and it should have crashed. It does not. because the lowest level of programming a third party developer can use in FS20 Community is Web Assembly, which is put in a sandbox system. It cannot write anything, update anything or hurt the game… it cannot write files…
Microsoft and Asobo have made an open system. That is a valuable feature and the Community folder is needed to keep this game alive and kicking. So I agree with your thanks to Asobo, but as a developer, I don’t like your conclusion about Community. I feel blamed for things. Yes, maybe there was a faulty addin. You removed it. But with this negative story about Community you blame everyone who is working hard (without pay) to let players enjoy more of the world in FS20.