Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
No one should ever write code like that and no experienced LabVIEW developer would find that anywhere close to acceptable. And there are no doubt analogs in the text-based world, except you may not even know it because the structure isn’t as visible.
Also, there are certainly test frameworks for testing LabVIEW code. NI has a few but then JKI, a third party company, has multiple testing frameworks including Caraya, which is similar in philosophy to something like FsUnit for F# or Elixir’s ExUnit.
https://github.com/JKISoftware/Caraya
Mandatory fanboi mention, and IMO a gross omission of the article:
https://enso.org/ (née Luna)
- an open-source language & IDE which aims to insta-kill all the "vs. textual programming" arguments by keeping a strict 1:1 visual<->textual representation translation as a core feature of the language. Go check it out!
Related posts
- Ask HN: What are your thoughts on no-code tools like Microsoft's Power Automate?
- Platform for mixing Python, Java, JavaScript and much more
- Enso – a programming language with dual visual and textual representations
- Enso – Get insights you can rely on. In real time
- Modern Data Modeling: Start with the End?