Advantages of each programming language

[cierra_shawe]

Hi everyone!

Although it is only 3 days until our first regional, we have yet to solidify what programing language will be used. I was wondering what the advantages of each would be, and availability of teams who would be able to help at the regional. Also any other tips to help our rookie team out would also be great!

[Alan Anderson]

Use whatever language you're most comfortable with. What did you program with while you were developing and testing your robot?

[basicxman]

Originally Posted by cierra_shawe

Although it is only 3 days until our first regional, we have yet to solidify what programing language will be used.

I sincerely hope you've already programmed your robot

Originally Posted by cierra_shawe

I was wondering what the advantages of each would be, and availability of teams who would be able to help at the regional. Also any other tips to help our rookie team out would also be great!

There are tons of threads out there on this, but I'll offer some quick points

• There's a fair amount of support at regionals in all three official languages, but LabVIEW seems to take a majority
• I'm not American, but I believe many American high school comp sci courses (specifically AP level) teach Java
• Java and C++ have a fair amount of similar syntax
• SmartDashboard can be extended with Java, default Dashboard can be extended with LabVIEW

EDIT: If you need specific real-time help, PM me

[andreboos]

Java and C++ compile and deploy much faster than LabVIEW, or at least that was the case last year. We use C++, and it takes 5-10 seconds to compile and 3 to deploy our code, which really cuts down on programming development time. LabVIEW takes several minutes. That said, LabVIEW is far easier for beginners at programming.

[basicxman]

Originally Posted by andreboos

Java and C++ compile and deploy much faster than LabVIEW, or at least that was the case last year. We use C++, and it takes 5-10 seconds to compile and 3 to deploy our code, which really cuts down on programming development time. LabVIEW takes several minutes. That said, LabVIEW is far easier for beginners at programming.

LabVIEW also has some very nice debugging tools.

Disclaimer: That being said, I use C++ for the robot and this year quite a bit of Java for the dashboard and won't be switching anytime soon.

[Ziv]

if(youKnowAnyLanguage) {
    use(theLanguageYouKnow);
} else {
    read(WPILibCookbook);
    if(youUnderstoodAnyOfThat) {
        use(java); // C++ is an option, but it's a bit fiddly.
    } else {
        use(labview);
    }
}

An experienced FRC programmer using Java (and presumably any other language) can get a passable program running in a matter of hours, not days. Nevertheless, start learning and/or coding ASAP!

[basicxman]

Originally Posted by Ziv

// C++ is an option, but it's a bit fiddly.

Care to elaborate?

[Ziv]

Originally Posted by basicxman

Care to elaborate?

If I were teaching someone to program and I had a choice as to whether or not I had to explain memory management, I would choose not having to. But it's not that big of a deal. Besides, every language has its own special problems .

[basicxman]

Originally Posted by Ziv

If I were teaching someone to program and I had a choice as to whether or not I had to explain memory management, I would choose not having to. But it's not that big of a deal. Besides, every language has its own special problems .

Memory management is an important topic in Java, the severe memory leak in SmartDashboard this year is a perfect example.

[carrillo694]

Originally Posted by basicxman

Memory management is an important topic in Java, the severe memory leak in SmartDashboard this year is a perfect example.

For the purposes of programming a robot in only three days and not testing it until practice day, memory management probably is not their primary concern

cierra_shawe, what programming languages are you or those on your team familiar with? If the answer is "none," I am leaning towards recommending LabVIEW. Not because it is necessarily easier, but because its control structures seem more intuitive than the syntax that comes with Java or C++. If the answer is "some," then I would go with Java, because its WPIlib implementation seems simpler than the C++ implementation, which makes it easier to learn. But I could be wrong about that, since my team uses Java. At least you will not need to be concerned about memory management if you are unfamiliar with it, unless you are doing computer vision, which I do not recommend if you are testing your robot for the first time in a few days!

[basicxman]

Originally Posted by carrillo694

If the answer is "none," I am leaning towards recommending LabVIEW. Not because it is necessarily easier, but because its control structures seem more intuitive than the syntax that comes with Java or C++.

I really think this depends on your background. LabVIEW control structures can be intimidating and non-obvious at first. The way a LabVIEW program executes is quite a bit different than a C++/Java program. If a student has a background or enjoys math or algorithms they might find C++/Java more intuitive to them. If a student has a background in electrical they might find LabVIEW more intuitive to them.

Originally Posted by carrillo694

If the answer is "some," then I would go with Java, because its WPIlib implementation seems simpler than the C++ implementation, which makes it easier to learn.

I don't think this is entirely correct, the components inside the WPILib for Java and C++ are abstracted at essentially the exact same level - it's really about which ever language you're more comfortable with.

[Jared Russell]

I would argue that starting from scratch, it is easier for a student programmer to use Java (for FRC) than C++ (for FRC).

I cannot count the number of times I have been asked to help a team with C++ and seen problems like the following...

Victor myVictor(1);

myVictor->set(0.0); // Error!

Victor *myVictor = new Victor(1);

myVictor.set(0.0); // Error!

Victor *myVictor;

myVictor->set(0.0); // Error!  You declared, but did not substantiate, your Victor!

void SomeFunction(Victor victor)
{
victor.set(0.0);
}

Victor *myVictor = new Victor(1);

SomeFunction(myVictor); // Error!

void SomeFunction(Victor victor)
{
victor.set(0.0);
}

Victor myVictor(1);

SomeFunction(myVictor); // Still an Error!  You are making a copy of your Victor!

In Java you don't have to worry about objects on the stack vs. the heap (they are all on the heap), pass by reference vs. pass by value (always pass by value, even if your "value" is itself a reference to an object), memory leaks, C++ name mangling in compiler errors, initializing static class members outside of the class declaration, etc.

[blackflame2996]

Originally Posted by Ziv

if(youKnowAnyLanguage) {
    use(theLanguageYouKnow);
} else {
    read(WPILibCookbook);
    if(youUnderstoodAnyOfThat) {
        use(java); // C++ is an option, but it's a bit fiddly.
    } else {
        use(labview);
    }
}

An experienced FRC programmer using Java (and presumably any other language) can get a passable program running in a matter of hours, not days. Nevertheless, start learning and/or coding ASAP!

nice.