Does anyone know why NI-DAQmx 19.0.0 for LabVIEW 2019 has dependencies on LabVIEW 2018 SP1 f3 & LabVIEW 2014 SP1 f11 runtimes?
This seems ridiculous.
I can install the DAQmx 19.0.0 driver itself without these dependencies, but if I try to add MAX configuration support and LabVIEW 2019 support I then have to install 2 more old versions of the runtime???
Does NI realize how big the installer is when you build one using these functions? Do they realize how much people hate being asked to install gigabytes of dependencies to get even a simple little DAQ app to run? It's a big obstacle to people adopting LabVIEW based solutions. I work with over 100 engineers who often install my software... initially. But they are looking for the earliest opportunity to replace it with some python code so they can remove all the ridiculously huge NI dependencies and runtimes from further clogging up their already bloated computers.
I groan every time I have to install another runtime. Image how people feel who haven't already bought into the NI ecosystem!
This situation is not new. The NI Package Manager has at least helped in some cases to get the right dependencies onto your computer. Now NI needs to put some priority on tidying up those dependencies!
Troy - CLD
"If a hammer is the only tool you have, everything starts to look like a nail." ~ Maslow/Kaplan - Law of the instrument
