[dmitch]

Originally Posted by keehun

Ok, well, if all the other guys want Java, then I say just stick with Java. One of coolest things about FIRST is that it teaches you the benefits of working as a team. For my programming team, majority of the guys know Java, but we chose C++ as a preference for two reasons:

1. We didn't want to try a "new" language for the cRio platform
2. C++ was proven to work and was fast
3. We all kinda-sorta knew C++
4. Being a captain, I pushed for C++ after having a bad experience with LabView last year
5. Our mentor is like a 30 yr veteran in the field of C++ and Systems Networking

After working with it for a couple weeks, I feel C++ was the right choice, but I know that Java or LabView would've equally been fine. Maybe not LabView, but that's only because trying to wrap all the programmer's mindset around the real-time execution paradigm is difficult. Even the 30-yr C++ veteran mentor (he's also a huge expert in Java) didn't know why LabView behaved the way it did -- that was the real downer last year. Also, we wanted to diff and git with C++.

What was the bad experience you had with labview last year? It would help because that's what our team is using it would help to have an idea of any errors we should expect. Thanks in advance!