>bloat ui

>>106122395 (OP)
Yeah it's no wonder planes crash due to human error still. Why isn't all this shit automated who needs this many buttons and levers holy shit it's like Jules Vernes designed this shit

Most software would look like that if every function had to be directly accessible without being hidden behind a menu, config flag, etc.

You might not like it but this is what peak UI performance looks like.

>>106122418
Sweaty it's called vibe flying, we just have claude control the plane

>>106122395 (OP)
If you really need to troubleshoot a mechanical component, it's best to lay all the steps out to give you some options in case you need to bypass something that failed.

>>106122418
Flight computers are quickly catching up to human pilots in errors leading to crashes.

>>106123246
yeah it's the settings menu and the ui

>>106122395 (OP)
Ideally the cockpit should just be a terminal and a keyboard. To take off, the pilot simply enters
>echo 15 > /dev/flaps
>echo 100 > /dev/throttle

>>106122395 (OP)
First, slash it by maybe 30% as flight controls are duplicated.

Second, how else would you do it? A plane has many, many functions, from the radio to the flight controls to landing gear to 2-4 engines to deicing to the fasten seatbelt signs. In the physical world you can't have progressive disclosure or hierarchy menus. You could go the Tesla route and bury everything behind a single touchscreen, but do you want your pilot to navigate a menu tree in an emergency?

>>106123751
>echo >
>cannot overwrite existing file

>>106122395 (OP)
Buy a new Cirrus SR22T G7 if you want a clean UI