4 ms·
I’m not sure about that. I used to use LabView and its various libraries often. The whole thing felt scattered and ossified. I’d take a python standard library
by wasmainiac 11mo ago
I’m not sure about that. I used to use LabView and its various libraries often. The whole thing felt scattered and ossified. I’d take a python standard library any day.
- pjmlp 11mo agoYet most EE engineers rather use a graphical tool like LabView or Simulink. Not everyone is keen doing scripting from command line with vi.
- sallveburrpi 11mo agoMaybe it’s different for those actually working in the profession and n=1 but in my (many) years of studying EE I never used these tools even once.
- amluto 11mo agoI once interned at a lab that used a piece of surely overpriced hardware that integrated with Simulink. You would make a Simulink model, and you’d click something and the computer would (IIRC) compile it to C and upload it to the hardware. On the bright side, you didn’t waste time bikeshedding about how to structure things. On the other hand, actually implementing any sort of nontrivial logic was incredibly unpleasant.
- wasmainiac 11mo agoHahaha yep, so much clicking after One day my finger was actually sore.
- wasmainiac 11mo agoNo not really, depending on the application Cpp or python has been the language of choice in the lab. Labview was used because it was seen as easy to make UIs for operators in production facilities, but even that was a regrettable decision. We ended up rewriting LV business logic in c# and importing it as a lib into a LV front end.