It would be good to see a quick pros-and-cons. Not to start an endlesss “mine is better than yours” discussion but to learn which parts and design aspects work the best.
I have special interest because I’m writing a basic autopilot PoC for the WinIoT framework and of course would only like to take the best parts of both. Maybe it spins-off into something bigger then if it’s based on a solid design.
So far I think a modular autopilot where programmers feel they have access to extend any component without hacking should be the best. And non-programmers feel they have access to any data they require and can go fairly close to the internal functionality without learning to program (scripting/workflow/protocol support).
All that together with being able to sustain high loop times to keep the racers happy. Yes a tall order for a perfect system!
The story of Cleanflight is a good example of what I’m thinking about here. Where a professional developer (who admittedly writes slower code but more industry standard/best practice = “clean”-flight) meets a popular but not-so-clean Baseflight and out comes not only something which so far people think is better but also now is achieving the high loop speeds.
Anyway all good to see a broader platform support. In the long term we will probably converge anyway. Look at Cleanflight it’s almost like APM now they added GPS and other sensors. They even have extensive LED/Neopixel support which APM can only dream-of (out the box).