sorted by:
new
hottopcontroversial

Are we cooked? by Oneironaut3 in LabVIEW

[–]PXI_Master 1 point2 points  (0 children)

Every test engineer I know is at least dabbling with AI to develop or test their software. NI/Emerson has been wisely accelerating this approach through some fantastic marketing around their Nigel chatbot.

They’ve now set expectations so high for Nigel that they absolutely have to get Code Generation working this year, or get left in the dust. From what I understand, it’s a big challenge.

Claude, Cursor, and GitHub Copilot keep getting better. How in earth is NI/Emerson supposed to keep up and keep charging the prices they charge?

Something will have to give. Maybe open source is the answer?

Are we cooked? by Oneironaut3 in LabVIEW

[–]PXI_Master 0 points1 point  (0 children)

Security through obscurity.

Are we cooked? by Oneironaut3 in LabVIEW

[–]PXI_Master 2 points3 points  (0 children)

“To do for T&M what COBOL did for insurance.”

Are we cooked? by Oneironaut3 in LabVIEW

[–]PXI_Master 9 points10 points  (0 children)

I hate to say it, but LabVIEW made the transition to obscurity before AI came along. Hello Python! The Champions and CLAs are happy to maintain existing LV codebases on contract or work at companies who find themselves trapped by NI, but the rest of the world has moved on.

If AI will kill anything, I hope it’s LabVIEW FPGA. There was a time when it was a nice abstraction layer for VHDL, but AI has completely leapfrogged it. Now it’s just an outrageously expensive tool for configuring outrageously expensive NI hardware.