Linked by Thom Holwerda on Thu 5th Jul 2007 09:11 UTC, submitted by Tim Alson
Permalink for comment 253199
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/21/13 15:53 UTC
Linked by Thom Holwerda on 05/20/13 22:43 UTC
Linked by Thom Holwerda on 05/20/13 21:50 UTC
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
More News »
Sponsored Links



Member since:
2006-02-05
So the lack of (or extraordinarily poor) support of webcams, winmodems, scanners, and wifi cards in linux is something the kernel devs should be held accountable for? I don't believe that, and I doubt you do either.
The big problem with the linux way of having drivers as kernel modules is that any time the kernel changes, all the drivers have to change too. This could mean a recompile, but it could also mean more substantial changes. Windows has a layer of abstraction which gives vendors a stable ABI to work with, which means that when the kernel gets patched, drivers still work (the majority of the time anyways)
The linux way works when drivers are opensource, but the linux way makes commercial support pure hell. Since being business friendly is what windows is all about, it would make no sense to go that way.