[AdamHeard]

I'm not trying to be an arse, I'm just trying to get the reasoning behind it.

To me it sounds like e-stop is purely a punitive thing, I understand how FIRST has slightly different viewpoints on it.

Teams are going to be unsafe with the machines if they choose to be negligent, and an estop wont prevent that any more than disable in my opinion.

I know it's a bad practice, but when we're stressed working on stuff we sometimes take risks in terms of disabling the robot in an emergancy because we don't want to deal with the time it takes to e-stop, and it's hard to hit the disable key in a jiffy if you aren't hovering over it.

I'm more serious about safety than the FRC teams that are just a teacher and some students scrapping through their first year, so they are probably taking similar risks more often.

I can't be the only bad apple.

It'd be nice to just ditch e-stop and use disable for all cases. Or at least make estop not REQUIRE a reboot, maybe merely a 5 second timeout on the enable button (or a text box that pops up and reminds you to check for safety issues, then hit okay).