On 4/15/24 20:04, Tim via users wrote:
Samuel Sieb:
The only reason this is a problem for some manufacturers is because they
want to keep it proprietary.  Printers and scanners (and any other
hardware) that use open standards or provide open-source drivers work
great with Linux.  Compare the difference between NVidia and AMD or
Intel.  How often do you see people having issues with AMD or Intel
graphics compared to the never-ending issues with NVidia drivers?

I don't agree.  It's a PART of the reason, sure.  But not the only
reason.  When you're developing anything computing or electronics,
there's often years between conception of the idea and (allegedly)
finished product.

That seems very unlikely.

That's hard to do when you're trying to fit into someone else's product
that keeps changing.  You have to learn how it works before you can
develop for it, but then *it* changes and you have to start again.
Certainly, open standards help, but many of them don't exist when you
start, and others come into being in the middle.

In both electronics and computing you have developers who want things
done their way, and rival techniques vie for pole position.  Linux
seems very bad at continually re-inventing the wheel.  How many
different sound systems have we had over the years?

That has nothing to do with the hardware. The base sound card drivers didn't change, so it was irrelevant to any sound device makers.

If your design team and product is so stuck that you can't follow changes like that, then you're already in trouble.
--
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to