C or LabVIEW: CompactRIO

[ComradeNikolai]

1) What is your team planning to use?
I am planning on coding in C++, as it is what I'm most comfortable in. However, our coach may "strongly suggest" us to use LabVIEW... which would be unfortunate... When I'm faced with graphical programming, I just can't do it. It's not how I work.

2) What do you think will become the new standard?
I think, with nothing to base this off, most teams will stick with programming in C/C++, since most already have an established programming team which knows how to do everything in C, and so, there would be little to no advantage of using LabVIEW.

3) What will most rookie teams pick next year?
I think most will use LabVIEW because, as mentioned before, they have great support and many videos to help out. However, this year, many rookie teams, like mine, chose C over EasyC.

4) Do you think FIRST will give us the standard LabVIEW, or will we have a customized interface for the CompactRIO?
I thought I read somewhere that they ARE doing this, but it was about midnight when I was reading the thread...

5) We have some NXTs. Would programming them using LabVIEW be a good way to get some experience before next year's kickoff?
Yes.

6) Will there be any limitations to using LabVIEW? Will there be any features that are easily accessibly throught LabVIEW but require complex C? What are the main advantages/disadvantages?
One /*dis*/advantage: no commenting out a huge block of code that doesn't work and consequently confuse everyone reading it. See? I need comments!
FIRST / National Instruments stated that there will be parity between the libraries for C and those for LabVIEW, so I think that with an equal understanding of LabVIEW and C, there will be no difference in difficulty.