I think it is best to adopt a balanced approach. Recognize the strengths
and weaknesses of the available tools (e.g., LabView, C++ etc.) and use them
appropriately to solve the problem at hand. I think C++ and LabView make a
great combination. C++ is scaleable, very fast, provides excellent
multi-threading and real-time capabilities while LabView provides: ease of
GUI programming, robust control capabilities within a flexible framework.
Sure you could play nine holes with 7 iron only but it is best to use a
driver at the tee, an iron down the fairway and a putter on the green. I
have achieved excellent synnergy by using the above strategy.
John
"Labviewguru" wrote in message
news:506500000005000000D43E0000-998975444000@exchange.ni.com...
> James,
>
> Four and a half years ago, I answered and ad to a company I wanted to
> work for that required something called LabVIEW. I literally walked
> into the recruiter's office and asked her what it was. I then spent 1
> week learning it (okay, so I had programmed before, but that was 12
> years prior...you know, before the days of C++...) Back then, I had
> no idea what LabVIEW was.
>
> LabVIEW is very rapidly becoming a status quo language. I have
> watched the job searches for LabVIEW grow from none, to a veritable
> plethora of choices, at least, in key cities where high tech is king.
>
> LabVIEW, in my opinion, is gaining acceptance as a viable language for
> use not only in physics and testing, but now in many other
> applications, such as internet programming.
>
> I have heard it described as a niche language, one that only fits a
> certain need or is used in only certain industries. Last year, no
> one, I mean no one (sorry to the exceptions, but I am making a point
> here) was using LabVIEW for testing cell phones. But now, I am aware
> of several projects that do just that. Two years ago, I heard from a
> fellow that he was going to be the first one to use LabVIEW
> exclusively to control a complete manufacturing device. Now, I have
> worked on several projects where LabVIEW is not only the instrument
> and DAQ inteface, but the GUI and test executive as well.
>
> Some of your questions should be directed (and I assume they are) at
> National Instruments. NI is doing a great job, in my opinion, of
> getting the word out about LabVIEW. They have a remarkable help desk,
> a great palette of example programs the likes of which I have never
> seen in any other language, and have made alliances with a great many
> companies to co-market products. You are in the midst of what NI
> calls a revolution, and what could really be considered the transition
> from infancy to standard use of LabVIEW. With the addition of tools
> such as the GOOP toolkit, Realtime, and LabVIEW for Linux, LabVIEW is
> now more equal to other powerful languages. I forsee the day, quite
> soon, where many community colleges will be offering courses in
> LabVIEW. Yeah, you marketing guys at NI say "Whoa..that's our
> training income", but the idea of teaching the language at that level
> is one that is sure to guarantee LabVIEW will become standard. Oh,
> and calling LabVIEW a programming language is not something a lot of
> people do. It was considered an environment, a tool, but not really a
> programming language. I think that LabVIEW, or "G" as NI likes to
> refer to it, is now deserving of being called a programming language
> in every sense.
>
> Keep up the coding.