[apples000]

Roughly half the teams that I see at competition use software that has tank/arcade drive, buttons to toggle relays, and a joystick axis that corresponds directly to a motor set command. Most of the teams that do this, come up with very poorly written solutions full of race conditions, and other inefficiencies. Some people say that giving example code would ruin the learning experience for the teams, but in my opinion, working with well written code and doing things the right way is MUCH more valuable than making your robot work through poorly written software. Also, the more advanced teams are given the command based framework to write Java/C++ software. These teams don't have to learn about complicating concepts related to threading, thread interference, and atomic variables, but they still learn and get inspired, and they also get a well working robot. If teams were not provided the command based framework, many teams' robot software would contain threads, and would have many issues because threading is more difficult to do properly in Java/C++ than in LV. If teams are provided the command based framework, they also should get a simple example project (like the old IFI system had!). Who knows, maybe they wouldn't have to give us a control system that was complete overkill for 99.9% of the teams if we got example code.