From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
LabVIEW
LabVIEW subscription model for 2022
Solved!
@1100fps wrote:
My expectation is that 2016 will be quite functional for at least a few more years. The programs work, the software is usable, and you OWN the programming environment. How likely is it that NI will put forward features, or improvements in the next few years that will make the transition attractive. In your case, upgrading from 2016 would be expensive in any case. NI has an uncertain future. It looks like they are trying to maximize profits by pushing their support and sales off to third parties, and are in active talks to find a buyer. The resulting short term increase in profit may make them attractive enough to be picked up by a private equity group that is only interested in the return they can squeeze out. The future of NI is uncertain. It is prudent to coast on an existing license while exploring alternate options, or hoping the company makes a concerted effort to better serve their customer. Then again, there is always a chance that another party may rise up to create a credible replacement for LabVIEW, maybe even an open source environment community supported.. My license is permanent and frozen. When talking to young people about programming for industrial environments, I always mention LabVIEW, and suggest they look elsewhere. It's a sad thing.
They found a buyer.
https://www.emerson.com/en-us/news/2023/04-emerson-ni-acquisition
They also have some legal troubles.
The future is quite uncertain.
"maybe even an open source environment community supported."
I would be very interested in that. However, I think that is a rather daunting task.
"When talking to young people about programming for industrial environments, I always mention LabVIEW, and suggest they look elsewhere. It's a sad thing."
I can no longer recommend it either. It is sad.
@Taggart wrote:
They also have some legal troubles.
They seem to specialize in suing boards of directors for breaching fiduciary duty. It seems a business model in its own in suing happy America. I wonder what they would expect they should have asked instead. 😁
"maybe even an open source environment community supported."
I would be very interested in that. However, I think that is a rather daunting task.
That is wishful thinking. Nobody ever made anything substantial in that respect in the almost 40 years that LabVIEW exists. It's not just daunting but simply impossible without a few deka millions of funding. For something that is then given away for free? I don't think so. 😁 The Internet hype is long gone. Although thinking of it, if you put AI on it, it may still actually be possible to get that much of money. Who wants to start a 20 million fundraiser for a LabVIEW AI project?
@1100fps wrote:
How likely is it that NI will put forward features, or improvements in the next few years that will make the transition attractive..
That might depend on how much you value zooming. Sounds like a public beta is coming soon, with several IDE improvements. Although coming from 2016 you are getting other goodies like VIMs, Forward Compatible Runtime, CLI, Python integration, type specialized structure, and interfaces just to name a few.
@Hooovahh wrote:
@1100fps wrote:
How likely is it that NI will put forward features, or improvements in the next few years that will make the transition attractive..
That might depend on how much you value zooming. Sounds like a public beta is coming soon, with several IDE improvements. Although coming from 2016 you are getting other goodies like VIMs, Forward Compatible Runtime, CLI, Python integration, type specialized structure, and interfaces just to name a few.
Don't forget Sets and Maps, which was my biggest reason to move to 2019 when I did.
@crossrulz wrote:Don't forget Sets and Maps, which was my biggest reason to move to 2019 when I did.
Or TLS support on native TCP connections.
@IlluminatedG wrote:I'm not looking forward to 10-20 years down the line when companies have neglected investing in their own future and haven't been mentoring entry levels to become the next generation of senior devs in a decade or two. The talent pipeline issue that's going to be created will be the biggest issue methinks. There won't be entry level positions to gain skills beyond entry level unless you can subsidize your own side projects and practice beyond school...
This is just as big of a deal as the increased cost IMHO. Finding a mechanical engineer with a bit of Python or Matlab experience is about a billion times easier than finding one with LabVIEW experience, and it's not getting better. We haven't needed a full time LabVIEW dev, but we did need someone who could do a bit of it on the side. We've tried both training current hires and looking for new hires with some experience and can't find anyone that could do, say, 25% LabVIEW dev and 75% other work (like myself).
Though we've been on subscription a while now (Alliance member) I have told my bosses we need to put our resources into other languages since LabVIEW's future is so uncertain. We've just sent an offer to someone who can do 75% engineering work and 25% C/.net/Python related work, and we have no plans to train him up on LabVIEW. It's sad because I really enjoy programming it, but I think I'll be switching over the next few years to something more commonly useful.
@Hooovahh wrote:That might depend on how much you value zooming. Sounds like a public beta is coming soon, with several IDE improvements. Although coming from 2016 you are getting other goodies like VIMs, Forward Compatible Runtime, CLI, Python integration, type specialized structure, and interfaces just to name a few.
I don't need zooming myself but I'm cautiously optimistic about other IDE improvements. Any ideas what the other improvements are?
@BertMcMahan wrote:
I don't need zooming myself but I'm cautiously optimistic about other IDE improvements. Any ideas what the other improvements are?
I have heard a few things, but I can't be specific until the public beta is announced. Then I can link to publicly available things, like I did with Stephen's comment.
