It seems there isn't much Asobo working being applied to improving SimConnect. So I'm assuming there is a reason for that ... so this begs the question is WASM going to eventually be the only way forward?
I do admit that SimConnect is cumbersome with units of measure which are char/string when it should be enumerated (i.e. DatumName and UnitsName) and much more "odd" programming choices for an SDK.
SimConnect is also very slow.
I'd love a .NET 5 solution ... maybe something along the lines of .NET 5 Blazor WebAssembly ... not that I don't like JS and CoherentJS but they seem rather worky considering Microsoft already has better solutions available with .NET 5 and Blazor (C# no JS needed and far easier to debug).
Anyway, I'm just curious where MSFS SDK is going long term ... the JS/Coherent approach doesn't make a lot of sense to me especially when WASM seems to be fundamental part of the the SDK and Microsoft already have their own solutions.