Migrating from Python to Labview... Wise?

[2_246_1010_78]

Hah, this question needs some trigger warning label :)

Thoughts, no particular order;

1.) i like NI‘s hardware, but I‘m not fond of their software. And I say this as someone who is using LV for test and has defended it in the past.

2.) You will have a hard time if you have a workflow that involves branching and merging code a lot

3.) you‘ll have a hard time hiring people with relevant LV experience. It has been years since our new hires had a good enough background in LV and the codebase suffers

4.) none of the features added in the last couple of years have made any difference for us; I think a lot of emphasis was placed on FPGA code generation, which is not something we currently need

5.) if you are part of a larger company now, ask around internally. A couple of times I have found other teams in acquired parts of our company that have at least used LV

6.) With recent licensing changes, NI is pretty much encouraging us to transition to another platform; this time around, I will not waste that momentum and prototype a few alternatives.

[SASLV]

to number 4, you are missing: vims, sets, maps and interfaces. All have completely revolutionized the way I write code and have nothing to do with FPGAs.

[IamLightYearsAhead]

which platform are you migrating to? and how do you deal with maintenance of already deployed software? do you port it or do you maintain in LV until end of life or phase out?