[Ido_Wolf]

As apaird said, LabVIEW is used professionally for many different purposes, personally I once had a job interview in a telecommunications hi-tech company where they use LV to test all sort of things, so my experience in LabVIEW acquired by being a FRC programmer was much more well received than the average knowledge in written programming languages of a geeky high-school graduate.

To the OP, I've noticed you're from Israel and so I'd like to point out that we've had these discussions quite a few times in some regional-centric Facebook groups. My general conclusion is that LabVIEW would probably be ideal for beginning teams (unless their head programmer is an extremely competent C++ programmer or something), and other than that it's completely up to you. Some teams may prefer LabVIEW as visual representation of the program's "flow" might make things easier when dealing with robotics, others may prefer C++ because written language makes more sense to them as a programmer (not counting the new RobotBuilder thingy that I've yet to experiment with), of course there's a bunch of pros and cons for each.

The bottom line is - our regional just ended, which means you have almost a year to experiment. Just play around with both and consider which one feels better to program with, and which one you feel more comfortable with during the testing and integration phase. If you somehow feel limited by LabVIEW, C++ might be a better choice for you. Also, if your rookie team members have some background in C++, take a month and try to teach half of the new members to write robot code in LabVIEW and the other half in C++, and see if one group does better than the other. It's important to point out that it's hard to tell which of them would be more useful in the long run, after graduating from FIRST and high school, in case you choose to continue in engineering and/or robotics.