• wasnt broke dont fix

Sadly, security issues are still being found in sudo, so wasn’t broke isn’t entirely true. Though, whether or not Rust prevents a given security issue is strongly dependent on the kind of issue. Security issues arising from logical errors usually don’t get caught, there is only a guarantee for memory management issues.

• missing some configuration features of base sudo

One of the things sudo-rs does is implement only a subset of features to decrease the attack surface. A recent security issue did not affect sudo-rs because they simply did not implement the feature that had the (logic) bug. As with many things this is a trade-off.

Also ImageTragick was a thing, there are definitely security implications to adding dependencies to implement a feature in this way (especially on a shared instance). The API at the very least needs to handle auth, so that your images and videos don’t get rotated by others.

Then you have UX, you may want to show to the user that things have rotated (otherwise button will be deemed non-functional, even if it uses this one-liner behind the scenes), but probably don’t want to transfer the entire video multiple times to show this (too slow, costs data).

Yeah, it is one thing to add a one liner, but another to make a well implemented feature.

Also, the user experience is also bound to be much better when a manufacturer provides a tested and supported operating system, especially for “non-experts” for whom a terminal is an arcane inscription tablet.

That is only really a good solution for the few that live in the countryside. If sufficiently many people live close enough to one another without a shop, that is a issue that is best solved by improving planning and introducing local shops (reducing the distance all people in the community have to travel).