[rachelholladay]

Well Fletch1373 did a good job of laying out the basics of each language. I would definitely find out what your fellow students and mentors know because if someone already has experience in a language then that is a major pro.

Personally, my team goes with LabVIEW for a variety of reasons -
(Fletch covered this but I will repeat in my own words) Some languages are easy to learn but hard to master and some are hard to learn but relatively easy to master. LabVIEW is pretty easy to learn within the FRC environment. The framework provides a lot and the examples are useful. I've had to give quick LabVIEW lessons to a lot of rookie teams and its easy for me to show them how to, for example add a motor, include a solenoid, etc. The graphical element also helps out because sometimes that makes more sense and is easier to visualize.
The controls system hardware is produced by NI. That means that if we have any kind of issue we have one place we can go to for all our questions (I believe Mr. McKaskle will agree that we ask plenty of questions..) If we have a problem, its NIs hardware and software, so they can help us from all angles and can debug issues faster.
More teams in our area use LabVIEW. If we need help, there are more people we can turn to. Conversely, we can help more rookie in our area. It helps to have a local community.

If you are interested in LabVIEW I agree FRC Mastery is a great place to start. I learned LabVIEW by spending a week of my summer a few years back watching two or three a day while working through examples. (That's right, I know how to spend my summer vacation in style..)