4 ms·

At this scale, the difference doesn't matter. "No support" means "only runs on". Those software makes everything we use daily and we depend our literal lives on

by okanat 3y ago

At this scale, the difference doesn't matter. "No support" means "only runs on". Those software makes everything we use daily and we depend our literal lives on. No sane management will risk billions of losses, the literal production and accounting of the company or possible loss of human lives on some ideological or aesthetic preferences on the OS. Moreover the licensing agreements usually prevent the licensees from even trying such things. Compared to their licensing fees, RHEL or SLES are a cent to a 100 bill. Technically the programs may or may not work. Those programs are large and even if you have access to the source code, they can be very tricky to understand. Making all of their parts and their extensively used C++ plugin systems work in a foreign distro is probably harder than reverse engineering some hardware. They are not "janky commercial software". People can and do produce cars, planes, UAVs, latest supercomputers and ICs, satellites and even nuclear warheads with them. Linux userspace libraries don't provide stability or featureset guarantees and distros patch them and worsen the compatibility. Enterprise distros guarantee them and take responsibility for that. In addition the commercial software developers and their customers get premium tier support often connecting you to the developers who curated the distro. You cannot expect community to provide any of that, especially after many years of tradition of almost intentional breaking.

hedora 3y ago
Any company building safety critical stuff should be using a separate set of hardware to validate the CAD designs. Even with ECC memory and machine check exceptions, processors still corrupt stuff and make mistakes. On a practical note, I've dealt with $$$ software that only runs on enterprise Linux or particular versions of Windows. Without fail, it has been buggy as hell, and crashed if there was a slight breeze outside or under gibbous moons. Examples: "When you boot the computer, first click this, then that, and finally this." "We all need to share this one laptop. No one may use the laptop for anything but this one flow in this one program because the laptop's OS install is irreplacable, and the equipment it drives costs $250,000" "Don't run anything in the background because their verification kernel was only tested with two cores, and we can't buy CPUs that old any more" "Don't turn the printer on until after the UI is done booting up because if it sees an HP vendor ID on the USB bus it thinks it's a spectrophotometer or a license dongle or something"

by okanat 3y ago

hedora 3y ago

Any company building safety critical stuff should be using a separate set of hardware to validate the CAD designs. Even with ECC memory and machine check exceptions, processors still corrupt stuff and make mistakes. On a practical note, I've dealt with $$$ software that only runs on enterprise Linux or particular versions of Windows. Without fail, it has been buggy as hell, and crashed if there was a slight breeze outside or under gibbous moons. Examples: "When you boot the computer, first click this, then that, and finally this." "We all need to share this one laptop. No one may use the laptop for anything but this one flow in this one program because the laptop's OS install is irreplacable, and the equipment it drives costs $250,000" "Don't run anything in the background because their verification kernel was only tested with two cores, and we can't buy CPUs that old any more" "Don't turn the printer on until after the UI is done booting up because if it sees an HP vendor ID on the USB bus it thinks it's a spectrophotometer or a license dongle or something"