Commentary

Alexander Wolfe
 

Sparks Fly As Linux Kernel Guy Quits In A Huff

There's another item to add to my list of 7 Reasons Why Linux Won't Succeed On The Desktop. An Australian doctor who spent his spare time working on the kernel says desktop performance is suffering because Linus Torvalds and company are only concerned about enterprise users. He got so ticked off he quit Linux in a huff, and made some pointed comments about Linus.

There's another item to add to my list of 7 Reasons Why Linux Won't Succeed On The Desktop. An Australian doctor who spent his spare time working on the kernel says desktop performance is suffering because Linus Torvalds and company are only concerned about enterprise users. He got so ticked off he quit Linux in a huff, and made some pointed comments about Linus.The doctor/developer is named Con Kolivas. His tale is pretty important, especially in the context of all the push-back to my criticisms of desktop Linux. Essentially, Kolivas agrees, but for completely different reasons. His take: "The desktop PC, for which Linux started out as being developed for, [has] fallen by the wayside. . .The developers were all developing for something that wasn't the desktop. They had all been employed by big name manufacturers who couldn't care less about the desktop (and still don't) but want their last 1% on their database benchmark or throughput benchmark or whatever."

To remedy the problem, Kolivas wrote something called the -ck patchset, which is a bunch of code that changes the kernel's CPU scheduler to improve desktop performance.


More Global CIO Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Long story short, Kolivas's fight to get his patches folded into the kernel was rejected. Adding insult to injury, another developer wrote a scheduler, which did get added to the kernel. At his wit's end, Kolivas decided to stop working on Linux, charging that the development process is completely disconnected from the needs of normal users ("You know, the ones who constitute 99.9% of the Linux user base," he says.)

But wait, there's more! Kolivas raises the very interesting point, which rings true, that the people who maintain the Linux kernel are so intimidating to the average Linux user that Linus and his inner circle never even see many bug report from those average folks. Here's how he explains this:

"The Linux kernel mailing list is the way to communicate with the kernel developers. To put it mildly, the Linux kernel mailing list (lkml) is about as scary a communication forum as they come. Most people are absolutely terrified of mailing the list lest they get flamed for their inexperience, an inappropriate bug report, [or] being stupid."

Which leads to his parting shot at Torvalds:

"Yes of course the kernel developers are fun loving, happy-go-lucky friendly people. Just look at any interview with Linus and see how he views himself."

Kolivas's feelings aside, the salient question is whether Con is correct that desktop Linux is suffering because of an over-focus on enterprise users and server Linux. A sober look at the situation, from the perspective of the Linux brain trust indicates that that's probably a sensible approach.

Linux is in widespread use on servers, and there's actually a business surrounding this. Desktops, not so much.

I can't tell you whether Kolivas's contributions would have actually improved the desktop performance of the kernel, though on the face of it his ideas make sense. Whether he's the best guy to implement them is another story. Clearly, Kolivas is a polymath, and a highly intelligent one at that. (Now that he's quit Linux, his new project is to learn Japanese.)

The whole tale tells us something else, which runs counter to the image of Linux. Most of us think of Linus, the Linux folks, and indeed the whole open-source community as more fact-based than, say, the grubby commercial software sphere in which the Microsofties play.

Obviously, that ain't true. The Linux folks are just as prone to internecine warfare and backbiting as the rest of us..

Here's the link to the story, Why I quit: kernel developer Con Kolivas.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links