Thread: Curiosity on why most teams choose LabView
View Single Post
  #4   Spotlight this post!  
Unread 01-17-2010, 10:17 PM
jhersh jhersh is offline
National Instruments
AKA: Joe Hershberger
FRC #2468 (Appreciate)
Team Role: Mentor
  
Join Date: May 2008
Rookie Year: 1997
Location: Austin, TX
Posts: 1,006
jhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond reputejhersh has a reputation beyond repute
Re: Curiosity on why most teams choose LabView
Quote:
Originally Posted by Mike Copioli View Post
Our team uses Windriver primarily because our team has many students who are programmers. Programmers use programming languages. Labview is written in a programming language. I suspect that it was written in c/c++. If an individual desires to become a developer of products that use micro controllers they must know a programming language. If an individual desires to write desktop software they must learn a programming language. Having said that Labview is a great tool for people who are not programmers or have little knowledge of programming but need to create software that runs on a specific platform and need to do it fast. Gregs example highlights this. I personally enjoy the flexability that programming languages provide. They are universal allowing developers to write software for a variety of processor platforms. Although that the result may be the same, in some cases, whether you are using Labview or c/c++, to argue that one is better than the other is pointless because they are not the same thing.
Just FYI, LabVIEW is a programming language.
Reply With Quote