News for hackers. Stuff that matters.
Re:USS McCain collision ultimately caused by UI confusion by diggernet on Friday November 03, 2017 @01:09AM (#15616835)
It's not labor-intensive, it's attention-intensive. You want the person managing the speed to be focused on that. You want the person managing the heading to be focused on that. And you definitely don't want the officer to be distracted by maintaining course and speed when they need to be keeping track of what's going on around the ship.
Re:USS McCain collision ultimately caused by UI confusion by PeterisP on Friday November 03, 2017 @04:48AM (#15617614)
You want the person managing the speed to be focused on that if managing speed is still inherently and unavoidably attention-intensive - if modern control technology is able to automagically maintain speed at x knots, adjusting all the various engine control parameters to implement that, then an extra person in the loop only means an extra chance for mistakes or delays.
Re:USS McCain collision ultimately caused by UI confusion by cocoablazing on Friday November 03, 2017 @08:55AM (#15618773)
If the military learned a lesson from exploding a reactor with an automatic control system, you might never know - it's not required to be reported to the public.
Re:USS McCain collision ultimately caused by UI confusion by josefx on Saturday November 04, 2017 @05:04AM (#15624305)
If an automatic control system can blow up a reactor so can the manual one. You have a problematic design issue in both cases. You can also still assign someone to keep an eye on the reactor in case things go bad an have that person pull an emergency stop or warn the guy in charge. There is no reason to relay every little speed change through several people.