View Single Post
  #12   Spotlight this post!  
Unread 14-08-2008, 18:07
whytheheckme's Avatar
whytheheckme whytheheckme is offline
Registered User
AKA: Jacob Komar
no team
 
Join Date: Feb 2006
Rookie Year: 2005
Location: Providence, RI
Posts: 1,320
whytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond repute
Send a message via ICQ to whytheheckme Send a message via AIM to whytheheckme Send a message via MSN to whytheheckme Send a message via Yahoo to whytheheckme
Re: Labview: A Ballsorter

Quote:
Originally Posted by Dave Scheck View Post
I'm really getting frustrated with statements like this. While Labview may be AN industry standard, it is not THE industry standard. Go onto any job hunting website and search positions requiring Labview expertise. Now compare that to what you find for C++. I'm very confident that you will have a large discrepancy in the number of hits you find.
Someone else brought this issue up with me over PM. I didn't intend for my statement to sound like LabVIEW is REPLACING C (or any other language for that matter), but in the industry of data acquisition (which is a major part of the robotics industry), NI and LabVIEW is a leading technology. My point wasn't that LabVIEW beats out C or any other language, but that LabVIEW isn't some simpleton's tool. LabVIEW has awesome potential to do many things, and because it's so widely used, it's not 'worthless'.

I'm sorry if I made it sound like LabVIEW replaces any language in the global job market; what I intended to say was that for it's field (data acquisition), it is a leader, and in many ways, can be superior.

Sorry for the confusion,
Jacob
Reply With Quote