Quote:
Originally Posted by wt200999
The biggest benefits for using LabVIEW are that the complex things are easier (and quicker) to do. This is really where the strengths of LabVIEW start coming out, especially in the context of FRC. It is built to allow rapid development of complex systems. NI would be hard pressed to find customers if their only selling point was that the basics are easy.
|
Interesting. That's a perspective I haven't heard before, although it might be because of a different ideas of "complex". For doing sophisticated calculations and graphing, I preferred LabVIEW, assuming that what we were doing had a library available, but on the assembly line, the number of possible conditions we had to deal with made those LabVIEW diagrams awfully difficult to deal with.
Professionally, we always used it as a prototyping language, but when we had the real machine control, we used C or C++,or later we would C#, if the requirements would permit it.
It's always possible that I was doing it wrong, but I ended up cursing the mass of wires wandering about my LabVIEW diagrams, whether in FIRST or on my job, and I thought the nested if-thens were much cleaner and easier to understand.
To the original question: Obviously, as you can see from the differences of opinion, there's no right answer. If LabVIEW is working for you, don't fix it. Java and C++ are not "better". They're different.