Hacker News new | past | comments | ask | show | jobs | submit login

Sure -- MS made it impossible to review the code given to them by the manufacturer. It's a Windows', or in other words, proprietary software problem.

Do we have that problem with Linux?




Sure, off the top of my head Nvidia drivers contain a binary blob you don't get to see. Does it brick fake hardware? No but this is a very special case.

Is it out of the realm of possibility that a vendor could ship a kernel module with a proprietary binary that could damage your hardware? Absolutely.

Why would people accept these proprietary closed blobs over the open alternative drivers? Because the open drivers suck. Can you fix that? Not in the near term.

So how is this not a problem for Linux? It's a problem there too.


If you use Nvidia, then the open driver sucks. It is like GIMP sucks, and that's a very real problem. But the open drivers don't brick my hardware, GIMP doesn't go and send my shit to the cloud without me knowing it, and won't refuse to let me edit whatever I want (https://en.wikipedia.org/wiki/EURion_constellation).

This is a trade-off I am willing to make - that is all, nd I have mentioned it from the beginning.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: