Linked by Thom Holwerda on Tue 9th Nov 2010 22:24 UTC, submitted by koki
Permalink for comment 449337
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 06/18/13 22:33 UTC
Linked by Anonymous on 06/18/13 22:26 UTC
Linked by Thom Holwerda on 06/18/13 22:25 UTC
Linked by Thom Holwerda on 06/18/13 17:45 UTC
Linked by Thom Holwerda on 06/18/13 17:32 UTC, submitted by poundsmack
Linked by Thom Holwerda on 06/17/13 17:58 UTC
Linked by Thom Holwerda on 06/17/13 17:52 UTC
Linked by Thom Holwerda on 06/14/13 21:03 UTC
Linked by Thom Holwerda on 06/14/13 20:46 UTC
Linked by Thom Holwerda on 06/14/13 17:32 UTC
More News »
Sponsored Links



Member since:
2006-01-25
I'm all for idealist - they are the driving force of change. That said, this press release reads like propagandist drivel. Like most propaganda, the facts are all right, but the conclusions are all wrong.
Users do not need to be "warned" about this. Users are the reason firmware blobs exists: primarily because they scream bloody murder when some piece of hardware doesn't work. The vast majority of users do not care one bit about the fact that there is an opaque blob of bits in the kernel to enable their wireless card to function - they just want it to work.
Yes, it would be great if the hardware guys would supply the source code for this stuff. But they don't. Why don't these guys target their angst in the proper direction - at the hardware vendors?
Its not like this is a new issue, it has existed for years. The kernel guys have decided since this stuff doesn't "run" in any conventional sense, and since users want it, and since it doesn't affect the kernel's operation in any meaningful way, they just drop in into the source tree and move on. Its either that or refuse to include it, which would punish users for no good reason.
It is beyond ridiculous to say that Linus, or anyone connected to kernel development, are trying to "bait and switch" users.