A few issues come to mind (I&#x27;m sure there are others.)1. LabView doesn&#x27;t (or didn&#x27;t) really mesh well with things like git or mercurial so care must be taken making sure the C, C++, Rust, Python remain coupled with corresponding versions of LabView VIs.2. Sometimes there is a cultural gulf between the LabView developers and the C, C++, Rust, Python people. E.g. SpaceX may have some fun integrating California Software (C++, Rust, Python) with Texas Software (LabView)3. If you only have a limited number of LabView license seats, make sure your CI automata doesn&#x27;t eat all of your licenses.

Any pitfalls with python or C&#x2F;C++ i should be aware of? Agree that a large labview project is quite tricky

When I used to use LabVieW (shudder) I usually just made a VI to call python or C&#x2F;C++.A large LabView project can become tricky to maintain. Two of the largest LabView code bases are the flight software for NASA&#x27;s Cold Atom Laboratory and SpaceX&#x27;s real-time launch visualization GUI and both may have required substantial support from National Instruments.

Matlab works fairly well.Labview is a quick and dirty let’s do this and forget what happened. I considered looking up how to do something correctly then my second thought was to do whatever and turn it into a sub to hide the work.

Isn’t that what Measurement Studio is meant for?<a href="https:&#x2F;&#x2F;www.ni.com&#x2F;en-us&#x2F;shop&#x2F;product&#x2F;measurement-studio.html" rel="nofollow">https:&#x2F;&#x2F;www.ni.com&#x2F;en-us&#x2F;shop&#x2F;product&#x2F;measurement-studio.htm...</a>

Yeah that procedural text based alternative is called Python.

Trying to understand just how convoluted labVIEW&#x27;s GUI can get. Let&#x27;s say someone came out with an efficient, procedural, text-based alternative that can integrate with NI hardware - would it be a no-brainer switch?

Hardware engineers – would you rather use a procedural version of labVIEW?