There were some excellent response there. I would, however, like to make a few addtional comments.
First, LabVIEW is a compiler. The "source" code is compiled when the run button on the toolbar is pressed. The creation of an exe is done with the application builder that has been available for much longer than version 6. But, since the development environment is also a compiler, you will not see a signicificant improvement in execution speed when building an exe.
I originally started my NI programming with LabWindows v1.0. Back then, despite it's name, it was only available for DOS. I transitioned to LabVIEW when it was released for Windows 3.0. I had no great difficulties in making the transition. In fact, I had a great deal of fun in learning it and loved being able to "write" a program using only a mouse. Given some time and training, I think any text based programmer can do the same if he or she is willing to do so. Like anything else, there is a learning curve to LabVIEW but I don't think it's as steep as someone first starting to program C++ or VB.
I still do some occassional LabWindows programming but in my instrument control and DAQ applications, I simply find LabVIEW allows me to get the job done faster. If you have some specific imaging or motion application in mind, look over the tools available for each in LabVIEW and LabWindows and check over in those forums to see what they are using.
