Quote:
Originally Posted by cbale2000
Right, but experimenting with other languages is one thing, deciding you're going to switch languages before you have anyone who knows the language you're switching to is another.
I'm even a little curious as to what prompted a switch, for most teams there isn't a whole lot that you can do in Java that you can't do in LabView, and if they don't have anyone who knows the language, what made them decide Java was better?
|
I agree you probably want to see how much effort switching will be before you decide to switch. If you see at the beginning of build season that no one knows Java sufficiently well, you should probably stick with LabVIEW for at least one more season.
As far as what you can do with LabVIEW vs Java, there are definitely some things easier to do with LabVIEW and ther things easier with Java. Which one you choose depends a lot on what you want to be doing with the language.
On my team, we have stuck with LabVIEW since our programmers (me) dont feel like learning Java for FRC. In certain parts of the code I could see where Java would be more useful, in other parts I'm glad I'm using LabVIEW. We might make the switch next year, since none of our other programmers know any LabVIEW, but they know non-FRC Java.