Quote:
Originally Posted by Chris is me
I know for your regionals in particular, 1714 has several members who now know how to work with Labview who would love to help at competition time, if you guys need assistance.
|
Team 2502 will also assist in any way possible. We used LabView last year. We decided to go C++ this year. We're already liking it much better...
Our reason was for the following (but not exclusive to):
- Source control*
- Diff*
- Build time*
- Mentor expertise
- Student experience
- Cross Platform workspace**
- Preference
* I realize the new version of LabView has them built in. However, two things. 1. We decided long before we knew of the new LabView versions. 2. We have way more student/mentor expertise in C++ than in LabView.
** I know that in order to build, it requires WindRiver on a PC. However, any OS with a basic text/code editor can edit, merge, commit, and push changes to a repository (Git, in our case). Then we have a dedicated station where we pull all the changes, patch, build, and download. It's impossible to do that with LabView...
But truly to be honest, any language could get the job done equally well...