LabVIEW
Why labview 2019 cant open VIs written in 2020?
I'm very sorry if you felt attacked. It was not my intention. But I'm sure you agree that business is an important decision factor in anything that doesn't involve charity (and quire often even there).
@rolfk wrote:
@1984 wrote:
So all in all it seems to be a business decision. I wouldnt be surprised if a simple downconverter tool could be release which can convert higher VIs to lower labview version even without having LV on the PC.
crossrulz already answered your second question. As to this remark, if you didn't know, NI is a stock traded company with stock owners expecting a ROI that at least beats the market (which it hasn't really lately but they are still doing fine).
I'm sure your boss would be very delighted if you went to him and told him:
You: "You see I have this great idea that makes our products so much easier to use for our users. Can I work a few months on it?"
Boss: "Does it sell more products?"
You: "Hmm, no not really. It allows our users to use our products much longer before having to buy a new one."
Boss: "Get out of my eyes! Do you expect me to spend MY money to make our users buy less products? Do you want to still have a salary next month or rather sit on the street?"
But that argument is kind of thrown out the window with the inception of the subscription model (they have to pay to use the software whether or not they upgrade). So I do think there is a business argument for "backwards compatibility", though I currently think it is a weak argument when compared to so many other things I would like LabVIEW to have, removed, or refactored.
