Calling Out All Programmers

[daltore]

Originally Posted by Doc Wu

Isn't that kind of like asking PC, Mac, or Linux?

Whatever you choose is what's best for you.

<off-topic.rant>
I would like to point out that PC=Windows has only come about because of the Windows vs. Apple ads that have come up in the past few years to make it seem that Linux doesn't exist. In fact, "PC" is a generalized term that only refers to hardware, and can run any operating system that supports it.
</off-topic.rant>

[Robopanda6]

I don't mind Labview, it's easier to use than the other languages but it's just so messy. I'd rather lines of code than bits and pieces of it on my screen.

[davidthefat]

Originally Posted by daltore

<off-topic.rant>
I would like to point out that PC=Windows has only come about because of the Windows vs. Apple ads that have come up in the past few years to make it seem that Linux doesn't exist. In fact, "PC" is a generalized term that only refers to hardware, and can run any operating system that supports it.
</off-topic.rant>

PC = Personal Computer

if you want pure power, go get a main frame

[JohnFogarty]

Labview all the way, I have alot of experice with the G language so Labveiw is a snap. Though some of the FIRST references screw up I just use FPGA to create custom vi's.

[Jared Russell]

Java, even though C++ is my personal language of choice for general purpose programming.

Two reasons:

1. Easier for the students to learn Java than C++ "correctly"
2. I can run it on my Macbook.

[byteit101]

Originally Posted by davidthefat

if you want pure power, go get a main frame

if you want pure power, get a nuclear bomb, er, computer!

[davidthefat]

Originally Posted by byteit101

if you want pure power, get a nuclear bomb, er, computer!

Computers in a nuclear submarine is powered by nuclear power.

[dmitch]

Originally Posted by keehun

Ok, well, if all the other guys want Java, then I say just stick with Java. One of coolest things about FIRST is that it teaches you the benefits of working as a team. For my programming team, majority of the guys know Java, but we chose C++ as a preference for two reasons:

1. We didn't want to try a "new" language for the cRio platform
2. C++ was proven to work and was fast
3. We all kinda-sorta knew C++
4. Being a captain, I pushed for C++ after having a bad experience with LabView last year
5. Our mentor is like a 30 yr veteran in the field of C++ and Systems Networking

After working with it for a couple weeks, I feel C++ was the right choice, but I know that Java or LabView would've equally been fine. Maybe not LabView, but that's only because trying to wrap all the programmer's mindset around the real-time execution paradigm is difficult. Even the 30-yr C++ veteran mentor (he's also a huge expert in Java) didn't know why LabView behaved the way it did -- that was the real downer last year. Also, we wanted to diff and git with C++.

What was the bad experience you had with labview last year? It would help because that's what our team is using it would help to have an idea of any errors we should expect. Thanks in advance!

[FRC4ME]

619 is using Java this year. Many of the students are taking Java classes in high school, so it fits well. Also, it is so nice not to have to explain memory management to new programmers. C++ has far too many idiosyncrasies that just make new students go, "what the heck?!?" In my opinion, at least.

What I [i]don't]/i] like about Java is that we are limited to ME features. Java without generics has its own idiosyncrasies, too: ((Integer)vector.elementAt(1)).intValue() to extract an int from an array, for example.

[spartango]

192 is using java this year, primarily because students are learning it quite well in class, which leads to a smooth transition into the robotics world. We've noticed no real performance issues(we're sure they're there, but not big enough to hurt our bot) with the JVM this year...

What I don't like about Java is that we are limited to ME features. Java without generics has its own idiosyncrasies, too: ((Integer)vector.elementAt(1)).intValue() to extract an int from an array, for example.

FYI: There is a trick that we've used when developing for squawk(on SPOTs) that allows you to write Java 5 code(with generics etc) and still deploy it to the VM. FRC hasn't gotten around to integrating it with the SDK provided--i expect they will for next year--but if you really want those features...look up "retroweaver". There is also a comment about it in Eric Arseneau's presentation at google:

http://www.youtube.com/watch?v=aCM9KN2pzQE
around 28:00...

[j.cole]

If I knew (and by I, I mean anyone on my team) Java that's what I'd use but since LabView is easier and already known by the team that's what we use.

[_Tanto_]

C++ we've been using c++ for the last 6 years or so and we feel its the most flexible of the three