I'm looking into LabView but the graphic layering just looks like a goto call to me. The worst part is the data hiding. I know it's got logging and error trap capabilities but the developers I've met follow the microsloth/apple mantra; you don't know what's inside the box, you don't want to know and we're not telling. So even if it doesn't really suck it really lets crappy developers make pictoglyphics jibberish that really sucks.
This maybe my fault for not being comfortable with LabVIEW, but I've seen some real creepy stuff happen with the language. One of them being a constant boolean changing to false when it should be true upon closing a background process that communicates via UDP to a front end GUI. It kept it state by somehow attaching an indicator to it. Without it, it leaves the TCP connection hanging and you have to reboot the machine in order to close the connection.
Labview is riddled with bugs and very poorly documented. The latest version is incredibly unstable. If it weren't for the HUNDREDS of bugs in it (check the forums and known issues notes to confirm this fact) it would be a really neat programming language.
Labview is riddled with bugs and very poorly documented. The latest version is incredibly unstable. If it weren't for the HUNDREDS of bugs in it (check the forums and known issues notes to confirm this fact) it would be a really neat programming language.
Labview is riddled with bugs and very poorly documented. The latest version is incredibly unstable. If it weren't for the HUNDREDS of bugs in it (check the forums and known issues notes to confirm this fact) it would be a really neat programming language.
While I prefer open source software for our projects to help close the digital gap for the impoverished and help people across the income divide, I LOVE this video and the way it shows how irrational some people become against tools that remove barriers to entry based on obfuscation. Labview is great, it just is too expensive for our purposes.
Wires literally create spaghetti code. I have to hover my mouse over wire connection points and wait for tooltips to see what is connected. This slows down debugging where I could have instantly spotted a bug at a glance in a text language. Binary LabVIEW source files make it impossible to generate code difference reports. Revision control, code reviewing, and accountability are severely handicapped. You could use LabVIEW to do anything, but it will cost a lot more time and money than it should.
LabVIEW would be loved by the masses if it wasn't a proprietary language. You can only write LabVIEW using LabVIEW's IDE... which is the bane of my entire LabVIEW programming existence. I can write .NET code in a Notepad clone. Why can't I write LabVIEW code in an Paintbrush clone? :P
Currently in a Academic world use imperative code for make aplications. Is funny to see those codes, when only our developer understand the text (don´t care if that have remarks or no). I´m a post-graduate student and I only program in LabVIEW. I still remember the statement of one of my teachers: "LabVIEW is not a language for algorithms for positioning. Use C ++". I never did, nor never will, because I feel very comfortable developing applications in LabVIEW.
I'm looking into LabView but the graphic layering just looks like a goto call to me. The worst part is the data hiding. I know it's got logging and error trap capabilities but the developers I've met follow the microsloth/apple mantra; you don't know what's inside the box, you don't want to know and we're not telling. So even if it doesn't really suck it really lets crappy developers make pictoglyphics jibberish that really sucks.
generationalist 1 day ago
to summarize, LabVIEW sucks
jxhensley 1 week ago
labview sucks only to non users, we use it for our automotive and aerospace divisions...
LDSinners 2 weeks ago
This maybe my fault for not being comfortable with LabVIEW, but I've seen some real creepy stuff happen with the language. One of them being a constant boolean changing to false when it should be true upon closing a background process that communicates via UDP to a front end GUI. It kept it state by somehow attaching an indicator to it. Without it, it leaves the TCP connection hanging and you have to reboot the machine in order to close the connection.
jshowa7 1 month ago
@jshowa7 have you tried using a property value node for that boolean upon exiting the VI?
LDSinners 2 weeks ago
LabVIEW sucks. Period.
SunkuSai 3 months ago
This has been flagged as spam show
Labview is riddled with bugs and very poorly documented. The latest version is incredibly unstable. If it weren't for the HUNDREDS of bugs in it (check the forums and known issues notes to confirm this fact) it would be a really neat programming language.
ug5a2ld0 5 months ago
Labview is riddled with bugs and very poorly documented. The latest version is incredibly unstable. If it weren't for the HUNDREDS of bugs in it (check the forums and known issues notes to confirm this fact) it would be a really neat programming language.
ug5a2ld0 5 months ago
Labview is riddled with bugs and very poorly documented. The latest version is incredibly unstable. If it weren't for the HUNDREDS of bugs in it (check the forums and known issues notes to confirm this fact) it would be a really neat programming language.
ug5a2ld0 5 months ago
While I prefer open source software for our projects to help close the digital gap for the impoverished and help people across the income divide, I LOVE this video and the way it shows how irrational some people become against tools that remove barriers to entry based on obfuscation. Labview is great, it just is too expensive for our purposes.
tculhane 5 months ago
lul comic language is comic language
donvitofm 6 months ago
Wires literally create spaghetti code. I have to hover my mouse over wire connection points and wait for tooltips to see what is connected. This slows down debugging where I could have instantly spotted a bug at a glance in a text language. Binary LabVIEW source files make it impossible to generate code difference reports. Revision control, code reviewing, and accountability are severely handicapped. You could use LabVIEW to do anything, but it will cost a lot more time and money than it should.
EthanDavis31337 7 months ago
LabVIEW would be loved by the masses if it wasn't a proprietary language. You can only write LabVIEW using LabVIEW's IDE... which is the bane of my entire LabVIEW programming existence. I can write .NET code in a Notepad clone. Why can't I write LabVIEW code in an Paintbrush clone? :P
protospherex 10 months ago
@protospherex Nothing in perfect :S...
CapitanArdias01 9 months ago
Currently in a Academic world use imperative code for make aplications. Is funny to see those codes, when only our developer understand the text (don´t care if that have remarks or no). I´m a post-graduate student and I only program in LabVIEW. I still remember the statement of one of my teachers: "LabVIEW is not a language for algorithms for positioning. Use C ++". I never did, nor never will, because I feel very comfortable developing applications in LabVIEW.
CapitanArdias01 10 months ago
aaaaap language
nasseq 10 months ago
It's sexually really easy
sako36 10 months ago 10
Nice work guys.
niavteam 11 months ago
Google nexus one was tested with labview....
bboti86 11 months ago