LabVIEW
Do you still have fun using LabVIEW ?
@rolfk wrote:
@joshua.l.guthrie2.civ wrote:
I'm finding "fun" is becoming inversely proportional to the size of the LabVEW program.
I find that’s true for any programming language I worked with. The difference might be mainly that most other languages start with a much higher baseline of “unfunnyness” and the slope of increase is lower as the application grows larger. So the experienced pain over time often feels smaller in traditional languages but in absolute value you need to get in some fairly big applications to hit that crosspoint.
In Big O notation, unfunny-ness grows with O(N) for text based code, but O(Sqrt(N)) for graphical code. 😄
@IlluminatedG wrote:
@altenbach wrote:
In Big O notation, unfunny-ness grows with O(N) for text based code, but O(Sqrt(N)) for graphical code. 😄
Are you sure it's not O(N^2) because we have two dimensions of layout instead of 1?
Dimensions always ends up getting a though issue. Text code is at least 2 + i, as it has both a number of lines and line length and with i being the irrational dimension of function calls. LabVIEW would then be 3 + i dimensions as a diagram also has a z-order of objects (case and conditional compile structures, and the good ol’ stacked sequence, not to forget the overlapping of nodes, wires and structures). 😀
The overlapping of nodes would be analogous to packing multiple programming expressions into one to “proof” intellectual superiority and stacked sequences are a bit like text lines that are 100s of characters in length.
Multiple expressions into one chaining can be even improved by carefully omitting any unneccessary brackets to proof that you know the operator precedence rules of your language of choice right from your muscle memory. 😀
@Loucoume wrote:
Community is less and less active.
I completely disagree with this sentiment. I see more activity in the community than ever before.
1. There are 4 GDevCons happening (Europe, US, Australia/New Zealand, and Latin America) and the GLA Summit. These are all independent from NI and completely community driven.
2. I'm seeing a bunch of open-source tools being released by the community.
3. The Community Training Initiative (CTI) is getting its ducks in a row to open up LabVIEW training on the cheap. I'm hearing several people designing courses around what CTI has already done and contribute those back.
@Loucoume wrote:
I hope someday it will become free and open source so people will use it again.
We are convincing NI to make parts of LabVIEW open source. I am actively working on the Icon Editor. Allen Smith is actively working on Actor Framework. Sergio, the guy inside of NI who is charge of these initiatives, is asking NI for the next thing to go open. I am personally advocating for the Getting Started Window, especially since that would greatly help the CTI team. See this thread: Share Your Input: The Next LabVIEW Feature to Go Open Source
My ultimate goal is to make everything in LabVIEW that is VI based be open source. All NI would need to worry about then are quality control, the underlying (C/C++/C#) structure, and the compiler. Will this make LabVIEW free? No. Will we be able to convince NI they need to drop pricing due to not needing so much in R&D and maybe support? Possibly.
