Quote:
Originally Posted by brianelite
What do you mean teams couldn't test the cRio/Driver station until kickoff?
The REAL issue here is that FIRST continues to put amateurs in charge of developing the programming environment. Total disaster this year with C++, our code was blowing up for WEEKS into build season before the WPI guys fixed their library... absolutely inexcusable that these guys who cannot even compile their own library are given the task of providing the programming tools for hundreds/thousands of teams using C++... It is simply outrageous that after 2 years deployment FIRST had to scramble to put out a working cRio image/ robotics library in the final week or so...
|
What course of action do you propose, then? Instead of pointing fingers and blaming people for what's wrong, why not give some sort of constructive criticism on how to fix the current system? As evidenced by Team Update #16, FIRST does, at times, listen to the concerns of the greater FIRST community.