Hacker News Reader

Comment by transcriptase | Hacker News Reader

Show us on the doll where they’re wrong.

I'm guessing it's the fact that linux has in-tree drivers, so you necessarily need to "patch the kernel" in order to write/fix a driver for a non-standard compliant device?

How else is that supposed to work?

You either fix a driver in the kernel or a driver outside the kernel, it's not going to make that big of a difference to the person who has to fix it.

The difference is that the end user doesn't have to do it. Someone else is going to do it. Just like it is on Windows.

That only works because Windows has a large marketshare, the day it drops to 10%, users will have to write their own drivers as well

I was highlighting this as a similarity between them, but I see how my comment can be ambiguous. The average Linux user isn't currently writing their own drivers or compiling their own kernels, even with its tiny relative userbase.

I can’t see any blocker to publishing this as a prebuilt kernel module honestly.

For driver developers the above where you rebuild the kernel is a necessary step in developing the driver but now the above is done someone should make the trivial next step to make this into a prebuilt kernel module which are trivial to install for end users with no rebuild/reboot required. (I have built kernel modules before but I don’t have this laptop myself, sorry!).

I think the original comment was suggesting that Linux typically has end-user visible bugs like sound not working, not commenting on where they live.

Reply on news.ycombinator.com