Linus Torvalds admits 'buggy crap' made it into Linux 4.8

Re: There is lots of BUG_ON() all over the place

Why the hell are you people down-voting Patrick, exactly? I couldn't be because he is 100% correct and you can't be arsed to look at a Microsoft asshole the same way you look at Linus?

I have drank with Both people in Question. Linus is BY FAR more stable than Cutler, and Cutler is BY FAR more anal than Linus (to be fair, "coding standards" does not mean Good Code).

So what's the bitch, here?

* Microsoft can't have someone that actually cares? (One, they're allowed one, they HAVE to have one, otherwise Marketing and Business units would prevent *any* code from shipping.

* You can't believe that anyone is a bigger asshole (for the right reasons) than our Fearless Penguiny Leader? (Would you like me to sort that list by last name, company name, or date?)

- Bonus Round, Two Words: Steve Jobs.

My *completely* subjective and biased opinion (not that you asked for it, and if wise, you wouldn't) is that if Linus flames you for doing something that:

* Has been covered already.

* Is documented (can be googled in LKML)

* Linus has specifically said "Do not do this".

* Linus specifically tells YOU "Did you not see me tell him/her not to do that? WTF did you then do the exact same thing?"

AND THEN calls you out specifically as a dumb-ass...you are a dumb-ass.

Honestly, how many times do you have to tell someone not to do something? When does it *finally* become "OK" to tell someone they are fucking up in a way that leaves no ambiguity (just like the previous dozen times)? Ten? Twelve? A Hundred?

In MY shop the answer is "One Time" then I haul you out by your shirt collar, into HR, and I say: "Cut their final check now because I never want to see this incompetant shit again." Following instructions of the Team Lead is a basic function of one's job as a developer. That fact that Some Open Source folk have used "I contribute" to also mean "and since I'm not getting paid, I can fuck off on my code and ignore the Lead" can and should be used to eliminate that person as Open Source as with Corporate, don't want to follow the rules then you can piss-the-hell-off.

Not to put too fine a point on it, but Linus has been a hell of a lot more patient with some contributors than I (and most of my peers) ever would have been, by orders of magnitude.

@PatrickStar called it corectly.

Re: So before contributing

Then get shouted at publicly and profanities hurled in to the air, for just attempting to contribute to the open source Linux kernel.

Well, OK, I don't think anyone can be expected to read all of Linus' missives, but I do suspect that anyone aspiring to contribute code is well aware of the communication style in that team, including the occasional flame. That IS easy to discover upfront so you best grow a thick skin and put a bit of effort in re. code quality. That said, it's not great for new entrants, over time you may end up with an ageing pool of developers mainly shouting insults at each other :)

Re: So before contributing

>for just attempting to contribute to the open source Linux kernel.

Do or do not, no try there is.

Re: So before contributing

"In English: How can this right honourable linux developer be expected to remember something Linus said many years ago about something fairly obscure? Then get shouted at publicly and profanities hurled in to the air, for just attempting to contribute to the open source Linux kernel."

BUG_ON causes a kernel panic, then makes the kernel die.

You should not deliberately cause a kernel panic unless you have decided that the operation being performed has put the kernel in to a dangerous state - unless you are using it to debug, in which case the BUG_ONs need to be removed before pushing the code.

Therefore, this is not something "obscure", and the passage of time does not change what BUG_ON does, its intent or its well known use-cases.

It is also easily found in the KernelNewbies FAQ: https://kernelnewbies.org/FAQ/BUG