Databases
StackOverflow2013
Postsdbo
POWhat specific features of LabVIEW are frustrating to you?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat specific features of LabVIEW are frustrating to you?
    primarykey
    data
    text
    <p>Please bear with me: this isn't a language debate or a flame. It's a real request for opinions.</p> <p>Occasionally, I have to help educate a traditional text coder in how to think in LabVIEW (LV). Often during this process, I get to hear about how LV sucks. Rarely is this insight accompanied by rational observations other than "Language X is just so much better!". While this statement is satisfying to them, it doesn't help me understand what is frustrating them.</p> <p>So, for those of you with LabVIEW <em>and</em> text language experience, what <strong>specific</strong> things about LV drive you nuts?</p> <p>------ Summaries -------</p> <p>Thanks for all the answers! Some of the issues are answered in the comments below, some exist on other sites, and some are just genuine problems with LV. In the spirit of the original question, I'm not going to try to answer all of these here: check <a href="http://www.lavag.org" rel="nofollow noreferrer">LAVA</a> or <a href="http://www.ni.com/labview" rel="nofollow noreferrer">NI</a>'s website, and you'll be pleasantly surprised at how many of these things can be overcome.</p> <ul> <li>Unintentional concurrency</li> <li>No access to tradition text manipulation tools</li> <li>Binary-only source code control</li> <li>Difficult to branch and merge</li> <li>Too many open windows</li> <li>Text has cleaner/clearer/more expressive syntax</li> <li>Clean coding requires a lot of time and manipulation</li> <li>Large, difficult to access API/palette system</li> <li>Mouse required</li> <li>File namespacing: no duplicate files with the same name in memory</li> <li>LV objects are natively by-value only</li> <li>Requires dev environment to view code</li> <li>Lack of zoom</li> <li>Slow startup</li> <li>Memory pig</li> <li>"Giant" code is difficult to work with</li> <li>UI lockup is easy to do</li> <li>Trackpads and LV don't mix well</li> <li>String manipulation is graphically bloated</li> <li>Limited UI customization</li> <li>"Hidden" primitives (yes, these exist)</li> <li>Lack of official metaprogramming capability (not for much longer, though)</li> <li>Lack of unicode support</li> </ul>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCharlesB
    1. USJoe Zoller
    plurals
    1. This table or related slice is empty.
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat specific features of LabVIEW are frustrating to you?
      1. USTim
      1. VTFavorite
    2. VO
      singulars
      1. POWhat specific features of LabVIEW are frustrating to you?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhat specific features of LabVIEW are frustrating to you?
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI feel that the original title was just inviting a "Subjective and Argumentative" closure.
      singulars
      1. POWhat specific features of LabVIEW are frustrating to you?
      1. USEBGreen
    2. COI can agree with that. Thanks.
      singulars
      1. POWhat specific features of LabVIEW are frustrating to you?
      1. USJoe Zoller
    3. COWhat is the hidden primitives that you have mentioned?
      singulars
      1. POWhat specific features of LabVIEW are frustrating to you?
      1. USManoj
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload