This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new Linux.com!

Linux.com

How Linus copes with criticism - does it matter. Or does Linus NO really matter all that much?

Posted by: Peter Jakobi on September 02, 2007 12:22 AM
Actually, even if Linus says NO to something:


It really doesn't mean all that much.



Thus in case of NO, your important scrap of code, usage, requested licence,
or maybe your kitchen-sink just isn't in the mainline kernel itself. That's all.


Doesn't even disallow being a part of mm line of kernels.



Or that you are not allowed to do a really good job to maintain
a small set of patches against the mainline kernel. If you're good
enough a programmer and keep in touch, this patch-set wouldn't
even enlarge over time. And doing it that way would still gain you
merit in the eyes of other kernel developers.



NO merely says:


You're not going to be as lazy as you'd ideally like to be.


And that things like updating your code or using your code aren't
quite as convenient, as you'd like to be.


Or you might just fork the whole kernel.


Why not? If you're capable of doing this level of coding and
workload correctly? You're allowed to do that. That's a GPL issue.
As your right to do this is defined in there. And it's a right you have,
which has a resounding YES, including a YES by Linus.



So how important is Linus? Not that much at all. Except to your
attainable levels of zen bliss and laziness (you do know Larry Wall, don't ya?).



A NO by Linus however has one HARD requirement: Rechecking your
arguments and code both inside and inside-out. Linus has one failing.
His failure rate. He usually is either correct in his decision or at least
he makes a good point. Not necessarily specific to code. Maybe
merely specific to maintaining a manageable resemblance of
goal-oriented kernel-development. Another known failing of Linus:
He's good at it. Possibly to his chagrin. And to the detriment
of the time he can spent in zen bliss. Sorry. Ahem. In coding.



And you're welcome to argue that Linus is arrogant. You're
probably correct in saying this. But I'm probably also correct
in saying that it is arrogance backed by skill. And also, that
it's likely to be a prerequisite to time management for people
that have become victims to that kind of hot-seat. Such as
Linus' position in kernel development and direction.



So in a nutshell:



Just GET A GRIP, Sunny.



Oh, and do not forget to also get a grip on your ego, your fears, your senstitity, and your feelings of inferiority.

There's always a non-negative chance that you aren't. Isn't there?

Inferior that is.

And tell you what. That chance's even non-zero.



Just make sure of one thing.

Invest some of your time in reading up. And thinking. It won't hurt. Pinky swear. Much, that is. Just...



DO GET YOUR OWN GRIP, YOURSELF.



And be proud of it. And do not waste your money on that stale smelly pre-made one from your friendly neighborhood pimp...



This tirade on "LINUS - the incomprehensible, dangerous, ugly and whatnot bogey-man-cum-utterly-insensible-jerk biding HIS time under YOUR bed" herewith placed in the public domain :).

#

Return to How Linus copes with criticism