- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
Admin
Admin
Pot, meet kettle...
Admin
madarchod!
Admin
Trust me, if this guy did text-based coding, it would look just as bad. If he had any idea how to create subVIs (function) this wouldn't look half bad. This is basically a program with one giant function.
Admin
Since when is Windows 7 a WTF?
Admin
The NASA space pen story is false.
Admin
Admin
NASA and the Russians both used pencils to start off with; Fisher actually developed his pens independently and sold them to both the Americans and the Russians after he'd completed his development (although I think the Russians did adopt them later than NASA).
Admin
Admin
Actually, both of those are really bad examples, because they're very dense and messy.
Here's an example of one of the functions in the project I currently have opened. It doesn't have any comments, but I can tell you that every time you call it like this it adds a line to a log with timing info and error details (if there was an error) and optionally saves the log to a pipe delimited text file.
[image]Like other languages, LabVIEW has advantages and disadvantages. Some of the advantages include:
Some of the disadvantages:
Admin
Admin
I am working on a project that uses a somewhat similar "visual programming" tool for a lot of its functionality. In my experience these things: a) look great in demos to non-technical types (hence sales); b) can be good for cobbling something together quickly; c) become completely and horribly unmanageable if you try to do anything even remotely complex. And since in any non-trivial system (c) will predominate ...
Admin
Unfortunately, most LabVIEW code is written by end users, not programmers. I just inherited a pile of literal spahegetti code from the original author to see if I could clean it up, and eliminate a bunch of race conditions and a mysterious latch-up problem.
One of the first things that I did was create a concurrent state machine description of the logic, and a text-based specification of what all of the sub VIs did. The original developer was astonished. He didn't realize that you could actually design the software before writing it. I also introduced him to comments.
Moral of the story: Inheriting a large, badly written VBA application is bad. Inheriting a large, badly written LabVIEW application is very bad.
Admin
The above applies just as well for any text-based languages, so what was your point again?
Admin
Admin
madarchod, everyone in my compny has heard of fisher pen manufactrer.
Admin
Thankfully you can interface to most of the NI devices from C, and you don't need labview at all.
Incidentally, I have the interesting problem of an NI4462 card which was sold to me a few months ago as being "supported on Linux". This support uses a nasty binary blob kernel driver that is only available for distros about 4 years old (eg Mandrake 2008). Not impressed
Admin
I'm not really seeing the WTF here, any sufficiently complex LabView system ends up looking like that. Unless the WTF is LabView itself, in which case I wholeheartedly agree.
Admin
Admin
मादरचोद, तुम खुद को क्या सम्ह्जते हो?
Admin
In the case of the product we are using, it does not provide adequate tools, no - in LabVIEW, which I've not used, YMMD. For example on our project I have reimplemented a big wodge of it in Ruby - goodbye to unwieldy tangled and deeply nested diagrams, hello to succinct DSL-style notation with all the gubbins hidden away. This is the proper way to manage complexity, and is what a properly utilised text-based language will give you.
Nor does point (a) apply to text-based languages - a big score for visual programming tools in the sales and marketing area is that they are pretty and colourful and allow for an easy sell of the seductive myth that non-programmers can use the thing, but what looks good in demos can quickly unravel in real use.
Admin
Admin
Admin
पहले हिंदी सीखो बच्चे!
Admin
Admin
Admin
I think you could make just as sound an argument that no black people are reading this site. Why not go there?
Admin
Admin
I'm tired of these MF'n eels in this MF'n hovercraft!
Admin
Admin
Yes, there's your problem right there.
Admin
Racist!
What? Am I doing it wrong?
Admin
Not "any". "Many". If it's written well, it doesn't look like that, regardless of how complex it is.
Admin
Did you think I was advocating comments offensive to Indians?
Admin
Yeah, like CERN.
Admin
By the way, is it possible to avoid creation of new file for every function (subVI). I understand that it's not inherently evil, but it just freaks me out a little.
Admin
Yeah, last I heard, the actual Indians were off whining to Congress about how the Bin Laden's code name was Geronimo.
Admin
Thanks Yair, that's what I was looking for. Nice breakdown on the advantages/disadvantages too.
Admin
You may want to at least delete the context if you're going to write something silly.
Admin
Is that where Hoodaticus has been?
Admin
In that Snopes article, they twice refer to 100% oxygen atmosphere. Really? 100%? That doesn't seem right. Anyone know this for sure?
Admin
Admin
The difference is, in LabVIEW, it's impossible not to write ugly code.
Admin
Not that this is the place for it, but the answer is no, at least not in the way you want it. LV has two file types which allow saving several VIs inside a single file, but I'm pretty sure that's not what you're after, since you would still need to do all the creation of the VI, etc.
But it's not a big deal. You get used to it.
Admin
Admin
ah the good ol labview, the very first software project i was tasked to finish looked pretty much like that, in fact first thing i suspected when i opened the artice that it actually was that project. labview has its strong points but they dont lie in making large and complicated applications. its for pretty much what the name says its for, quickly tying together a lab setup by someone who is not nessecarily a programmer. pretty much any measurement equipment comes with labview drivers so for lab technicians its very simple to coordinate many instruments with quick hack of a labview. unfortunately it sometimes also gets used for lot more complicated things and then it ends up like that. it can be a horrorshow
Admin
Ah...I hate LabVIEW with a passion. Note that until a few years ago, you couldn't even comment out a portion of your code in LabVIEW, you had to disconnect the "wires" manually, tie together any that couldn't be left dangling, and then when you wanted to put it back in, you'd have to try and remember all the connections you removed so you can put them back again. Also, the GUIs generated by LabVIEW are the ugliest things you've ever seen. They may have looked slick in Windows 3.1, but now they look horribly dated with no real easy options to make it look modern. We had a horrible LabVIEW software for a propriety device we developed that looked like shit and ran like it too. I scrapped it and wrote a new software in C# using WPF and now it looks awesome, modern and gets rid of all the stupid GUI baggage that came from LabVIEW.
Admin
Note to self: Do not read the comments section of a WTF until 2 days after said article has posted and subsequent comment purge has occurred.
Admin
You can not to use on-line automatic translation to produce correct russian sentences.
There are no middle names in Russian, we use http://en.wikipedia.org/wiki/Patronymic#Russian