3 ms·
Labview. I hated graphical programming. I don’t even know why. Then I worked on this fairly complex real-time system with FPGAs and lasers and whatnot with seve
by jl2718 8y ago
Labview. I hated graphical programming. I don’t even know why. Then I worked on this fairly complex real-time system with FPGAs and lasers and whatnot with several people. Works first time. How does it work? Obvious. Encapsulation is obvious from the diagram. Comments barely needed. Need to make a change deep in the code that breaks an interface? Everything you need to change turns red. If something doesn’t look good, it probably isn’t. design patterns are obvious. Was it slow to write? Yes. Definitely. Were there times I was frustrated because I wanted to write some hasty junk imperative code? Yes. Labview made me do it right. Could all this be done easier with lexical code? Probably, but I rarely see it. Can you make a disaster out of labview? Yes; even worse maybe. But... it makes bad code harder to write than good code, and quite obvious visually.
- rthomas6 8y agoI could not disagee more. Sorry... But fuck Labview. I'll take VHDL over that mess any day.
- targafarian 8y ago> it makes bad code harder to write than good code In practice, I've only seen bad code drawn in LabVIEW; it was shocking for me to see a "good" code example once. But then fixing bad code (i.e., refactoring) is only pain and suffering compared to text-based languages. > quite obvious visually Agreed, you can see how confusing it is, but unfortunately that never stopped anyone from doing it that way in my experience. The only saving grace of LabVIEW is that you can now interface via C/C++ and avoid G (their "graphical programming language") altogether.