3 ms·

I don't hate it, I feel it's pretty good for talking to hardware, (understanding) multi-threading, agent oriented programming, message cues, etc. It's also fai

I don't hate it, I feel it's pretty good for talking to hardware, (understanding) multi-threading, agent oriented programming, message cues, etc. It's also fairly good for making money: the oil and gass industry seems to like using it (note: n = 1, I only did one oil n gas project with it).

duckmysick 2y ago
How does version control work with Labview? Also, since you;ve done only one project with it, how hard was it to pick it up and learn?
- bboygravity 2y ago
  I used Labview as part of a course in my degree (EE), so I already knew it. If you know other languages I would say it's very easy to pick up. Probably the easiest out of any language out there. Instead of heaving to guess/learn the syntax, you just pick functionality from icons/lists and drag and drop.
- jpeloquin 2y ago
  > How does version control work with Labview? Labview does have diff and merge tools. It feels kind of clunky in practice, kind of like diffing/merging MS Office files. In my experience people think of versions of LabView code as immutable snapshots along a linear timeline and don't really expect to have merge commits. Code versions may as well be stored as separate folders with revision numbers. The mindset is more hardware-centric; e.g., when rewiring a physical data acquisition system, reverting a change just means doing the work over again differently. So LabView's deficiencies in version control don't stand out as much as they would in pure software development. https://www.ni.com/docs/en-US/bundle/labview/page/comparing-vis-and-vi-hierarchies.html https://www.ni.com/docs/en-US/bundle/labview/page/comparing-...
- deleted 2y ago
  [deleted]