Linus Torvalds goes on epic rant about Linux kernel code

In today's open source roundup: Tornvalds loses it in an epic rant about kernel code. Plus: Lenovo 100S Chromebook review. And Google says Chrome OS is here to stay

Torvalds goes on epic rant about Linux kernel development

Linus Torvalds is not known for suffering fools when it comes to Linux kernel development. And he recently proved that again by going on an epic rant about some code he considered useless.

Silviu Stahie reports for Softpedia:

Linus Torvalds is known for his abrupt style, and he's never been shy about saying exactly what he's thinking, even if this got him in hot waters more than once. It looks like he's again in the middle of the discussion for all the wrong reasons after using some harsh language in the official mailing list.

Linus Torvalds is the undisputed leader of the Linux project, even if he technically works for the Linux Foundation. When he says something, people do pretty much one of three things: they listen, they do what they were supposed to do in the first place, or they leave the project. The latter actually happened quite a few times in the past few months, so it's not exactly something unheard of.

The problem is not that he criticizes the developers or that he corrects them when they make mistakes, but the strong language that he employs. In fact, he comes down so hard on them that they are unlikely to forget they have been scolded by Linus himself.

More at Softpedia

You can read Torvalds' comments in their entirety at the Linux mailing list link below, but here's a sample of what he said:

Christ people. This is just sh*t. The conflict I get is due to stupid new gcc header file crap. But what makes me upset is that the crap is for completely bogus reasons.

The above code is sh*t, and it generates shit code. It looks bad, and there's no reason for it.

Really. Give me *one* reason why it was written in that idiotic way with two different conditionals, and a shiny new nonstandard function that wants particular compiler support to generate even half-way sane code, and even then generates worse code? A shiny function that we have never ever needed anywhere else, and that is just compiler-masturbation.

Tell me why. Because I'm not pulling this kind of completely insane stuff that generates conflicts at rc7 time, and that seems to have absolutely no reason for being anm idiotic unreadable mess.

And it's a f*cking bad excuse for that braindamage.

Anybody who thinks that code like this is "safe" and "secure" because it uses fancy overflow detection functions is so far out to lunch that it's not even funny. All this kind of crap does is to make the code a unreadable mess with code that no sane person will ever really understand what it actually does. Get rid of it. And I don't *ever* want to see that shit again.

More at Linux Kernel Mailing List

Lenovo 100S Chromebook review

Chromebooks are red-hot sellers at Amazon, and now the Laptop Mag site has a full review of the Lenovo 100S Chromebook. Is it worth buying? Laptop Mag found the Lenovo 100S' price tag to be very attractive and noted the great battery life.

1 2 Page 1
From CIO: 8 Free Online Courses to Grow Your Tech Skills
Notice to our Readers
We're now using social media to take your comments and feedback. Learn more about this here.