Any help with programming?

[xXhunter47Xx]

Originally Posted by Ether

Is this true?

Sorry, the majority of teams at my local competition used C++/Java. Of course YMMV but that's just what I've observed.

[ThePremium6]

if you really are determined on changing languages, then i suggest LabView. its easy to use and in a string formal rather than line.

[MamaSpoldi]

Originally Posted by Alan Anderson

I've been a CSA at several competition events, and I try to keep track of what languages are being used. The first couple of years with the cRIO, they seemed about evenly spread, with Java trailing by a small amount. In the next few years, on average, LabVIEW and Java were each represented near 40%, with C++ teams making up the remaining 20%. Recently, Java seems to be increasing in popularity, at the expense of both of the other languages.

My impression is that C++ is much more popular among the "elite/powerhouse" teams. LabVIEW tends to be the language of choice for teams lacking either strong programming mentorship or school computer science courses. Java is used in Project Lead The Way, and that's what I think is driving its increased adoption.

For the kind of group programming we end up doing on the TechnoKats, I prefer LabVIEW. I find that it's much easier for people to get a sense for what the code is doing when they can "see" it instead of having to "read" it. The inherent parallel processing makes it less complicated to keep things modular, and there's a big win in keeping simple typographical errors from being an issue.

The comprehensive example code and tutorials included with LabVIEW for FRC are also a big factor in making it the programming environment I would suggest for a team without an experienced C++ or Java mentor.

Alan - Thanks for your insight on this topic. This is a great description of the who and why of FRC programming languages.

[hhoover]

I would also suggest looking closely before shifting from where your experience lies. If you have anyone on the team that has any understanding of previous year's code, then I would suggest staying with C++. If you don't, then you basically have a rookie programming team and you need to look to them to pick the language because they'll have to do the work.
From my perspective - although >I< really dislike LabView - I have found that the kids seem to pick it up fairly well, and the online tutorials, etc. are good enough. Without a strong mentor and / or capable kids, any elaborate programming is out of the question, but drive train + basic control of specialty devices should be possible with at least one or two dedicated students.

[Awesomegamer235]

i honestly dont like the new labveiw so if your using c++ dont switch

[nighterfighter]

Originally Posted by Awesomegamer235

i honestly dont like the new labveiw so if your using c++ dont switch

Can you expand on that? Why don't you like new LabView? What is different about it?

(Note: I've only touched Labview once, in 2010, so I have no idea if it is different this year).