If I was a manufacturer of planes I would probably figure out if it could be used. As a private individual - no way.
In this plane software example if I was a plane manufacturing org I could dedicate people to integrate it and test it.
There is a difference between an organization dedicated to making a product and a group of hobbyists coming together to scratch their itch. There is a scale, a threshold, above which you need big-org organization and sharing of responsibilities.
Small expert teams are fantastic for the sort of projects that can be done by small expert teams. For larger things there needs to be a bit more infrastructure and organization, or at least continuity of many, many years.
There is a threshold in software complexity after which one really needs lots of organized testing and fixing.
As a private user, if I fail the firmware update on my shiny plane, it's all on me. Unless there was some weird insurance to cover the costs.
In this plane software example if I was a plane manufacturing org I could dedicate people to integrate it and test it.
There is a difference between an organization dedicated to making a product and a group of hobbyists coming together to scratch their itch. There is a scale, a threshold, above which you need big-org organization and sharing of responsibilities.
Small expert teams are fantastic for the sort of projects that can be done by small expert teams. For larger things there needs to be a bit more infrastructure and organization, or at least continuity of many, many years.
There is a threshold in software complexity after which one really needs lots of organized testing and fixing.
As a private user, if I fail the firmware update on my shiny plane, it's all on me. Unless there was some weird insurance to cover the costs.