D
Don Y
Guest
On 6/10/2022 1:26 AM, Jeroen Belleman wrote:
Why is it *exposed* to hackers? Do you leave the door to the
building unlocked??
Really? I guess the folks who hack cars, pacemakers,
thermostats, babycams, etc. all must suspect Windows to reside
at the heart of those devices! No, wait... likely a Linux
variant! Or, something \"obscure and proprietary\". Ooops!
Who are you going to *CALL* when your Linux box shits the bed?
\"Hello, Linux community. We\'re a big company and are having
problems with one of our Linux-based products; can one of you
please help us as our PAYING customers are getting impatient
with us?\"
Who is going to maintain a fork of THAT kernel? What
are you going to do when some clever customer discovers he
can root your *device* and tinker with its code -- passing
his problems on to your support department (without mentioning
that he\'s tampered with the binaries)?
Who do you have ON STAFF to maintain your Linux-based products?
At what cost? Compare that to the licensing cost of a Windows
(or any other COTS) OS.
Do you have a printshop on-site to print your own manuals?
Your own semi fab? Sheet metal & paint shops?
Do you want to be in the OS business? Or, in the instrument
business?
On 2022-06-10 02:01, Don Y wrote:
On 6/9/2022 10:38 AM, Jeroen Belleman wrote:
The weird thing is that high-performance electronic instrument
makers use Windows. Look at LeCroy, Tektronix, Agilent, or whatever
they call themselves now. Bad choices, all of them. Why?
Why \"bad\"? What *can\'t* the kit do BECAUSE it runs on a
Windows platform?
It\'s bad because Windows is a system widely targeted by hackers,
and which needs patches and upgrades to remain usable. Any
of those may brick the primary purpose of the device, i.e.,
behaving like an electronic instrument. It becomes a maintenance
chore.
If it runs something obscure and proprietary, even though its
security may be lacking, it loses its interest to hackers.
Why is it *exposed* to hackers? Do you leave the door to the
building unlocked??
Really? I guess the folks who hack cars, pacemakers,
thermostats, babycams, etc. all must suspect Windows to reside
at the heart of those devices! No, wait... likely a Linux
variant! Or, something \"obscure and proprietary\". Ooops!
It\'s the same \"make or buy\" decision as with any component/IP in your
product (why not make your own cardboard shipping boxes?)
You *make* when you can add value. You *buy* when you can\'t
(\"value\" can take the form of reduced cost).
Embrace a bit of FOSS and now you need to become expert in that
\"component\" -- cuz there\'s no one you can CALL (or sue!) if
it fails to perform as expected. \"Linux, Inc.\"?
Fair enough. You could outsource that aspect if you don\'t
want to deal with. Besides, if a Windows-based instrument
fails because of some Windows deficiency, who are you going
to sue? Micro$oft? LMAO.
Who are you going to *CALL* when your Linux box shits the bed?
\"Hello, Linux community. We\'re a big company and are having
problems with one of our Linux-based products; can one of you
please help us as our PAYING customers are getting impatient
with us?\"
Who is going to maintain a fork of THAT kernel? What
are you going to do when some clever customer discovers he
can root your *device* and tinker with its code -- passing
his problems on to your support department (without mentioning
that he\'s tampered with the binaries)?
Folks who roll their own OS\'s either have trivial needs *or*
exotic needs that can\'t (economically) be met from COTS offerings.
Building on Linux is, effectively, rolling your own OS.
That\'s absurd.
Who do you have ON STAFF to maintain your Linux-based products?
At what cost? Compare that to the licensing cost of a Windows
(or any other COTS) OS.
Do you have a printshop on-site to print your own manuals?
Your own semi fab? Sheet metal & paint shops?
Do you want to be in the OS business? Or, in the instrument
business?