Linked by Thom Holwerda on Thu 28th Dec 2006 17:47 UTC, submitted by elsewhere
Linux "Proprietary kernel modules are flaky, out of date, and the bane of a Linux professional's existence - right? Maybe not. This three-part (part I | part II | part III) series makes a case for formalizing the uneasy truce between GPL-clean and 'tainted' modules."
Permalink for comment 196843
To read all comments associated with this story, please click here.
Closed Source Drivers
by hackus on Thu 28th Dec 2006 20:09 UTC
Member since:

Can't work.

The open source community moves too fast compared to our commercial competitors. We are not going to freeze the kernel API because some company doesn't want to update its driver.

The whole idea behind corporate intellectual property in the USA is write it once, then never fix it and patent it. Sue everyone if they make anything similar. Meanwhile, only fix it if you can charge ridiculous support rates per "incident".

The open source model doesn't work that way, because it relies on cooperation from users and the engineers at a fairly low level to fix problems.

The open source model also doesn't have a dividing line between user and engineer. Any customer can become and engineer, after all, they have the source code.

I think the efficiency of such a relationship speaks for itself.

Open Source engineers also have a love of the software we write, so we tend to care about bugs more than our commercial counter parts.

That means, we need open access for our customers to help us with those bugs, if they decide to do so, and we need the ability to debug the software sometimes in the wild.

After all, you can only test so much in the lab and sometimes customers have great labs they run the software in...also known as their organization.


Reply Score: 5