Earlier quoted context omitted.
How do they handle bug fixing though? What if one application wants a bug fixed, but another application is depending on the bug inadvertently?
The bug they fix is the bug that keeps the API contract intact. The first application gets its bug fixed, and the second application breaks because it was relying on a bug that didn't match the API contract. You program to an API, not to an implementation. The second application did the latter, and will therefore pay the price.
A regression is the kernel not giving the same result with the same user space
181–190 of 408 posts
Re: A regression is the kernel not giving the same result with the same user space
#182I'm always eager to read Linus's rants. I wish more of my coworkers were like him. I hate the environment where nobody reacts strongly to anything! If somebody fucks up hard and refuses to own up, I (or whoever's in charge) should be able to shout at them. It's only natural.
I disagree. To me he usually comes across as an asshole, albeit an extremely smart and accomplished one. A working environment where the person at the top can be relied upon to react to human failings with an aggressive, sweary [1] rant is not somewhere I ever want to work. [1] I'm aware that use of profanity in everyday speech is common in Finland. I don't mind swearing per se, but I find its over-use a bit tedious.
Actually what you are unaware of, might be that the use of profanity in everyday speech is actually very common pretty much anywhere in the world other than in the US&A where mince words and puritanism are still king.
Re: A regression is the kernel not giving the same result with the same user space
#183Makes me scared to even _consider_ contributing...
Re: A regression is the kernel not giving the same result with the same user space
#184"a return to a former or less developed state." See, it's the fact that Linus doesn't even know the real definition of 'regression' that makes me think I cant' trust him or anything he produces. That level of idiocy is simply intolerable.
The fact that you don't even understand the definition you quoted makes me...etc etc
Re: A regression is the kernel not giving the same result with the same user space
#185John Johansen will survive. Linus has made it incredibly damn clear what "no user space regressions ever" mean. See f.e the similar rant from 2012: https://lkml.org/lkml/2012/12/23/75 And it is his kernel so it is his rules. John Johansen admitted he messed up ( http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02539.html ) and promised to handle things better in the future so all is well.
> John Johansen will survive. We really need to stop excusing Linus's behaviour. Just because we may happen to agree with what he is saying doesn't mean we also have to agree with how he is saying it.
Re: A regression is the kernel not giving the same result with the same user space
#186Earlier quoted context omitted.
All my favorite languages are typed and I do agree with him.
Really? How so? If you have abstract types then you can easily make internal changes without making those changes visible externally.
1 - Not all changes can be kept internal, for example adding a new case to an ADT
2 - Internal changes can still alter the semantic of the API, even if from the outside everything still looks the same from the type system point of view
Re: A regression is the kernel not giving the same result with the same user space
#187Earlier quoted context omitted.
Disagree. It seems like Linus’ acerbic and direct means of communicating is the only thing keeping garbage code out of the kernel. He’s also made his views on “why not be nicer” well known. People need to get over it - his project, his rules. Plenty of other projects out there to hack on if getting yelled at when you disengage your brain is too much. Most of which don’t have the obsession with not breaking stuff for…
> acerbic and direct Isn't this just swearing? > the only thing keeping garbage code out of the kernel. I'm not sure if I'm buying that. It's possible, sure but on the other hand: It's not because the other way (i.e. communicating in a nice way, without all the swearing and direct attacks - which is imo not the same as direct communication ) hasn't been tried that somehow proves it won't work. E.g. I know repos where…
Re: A regression is the kernel not giving the same result with the same user space
#188John Johansen will survive. Linus has made it incredibly damn clear what "no user space regressions ever" mean. See f.e the similar rant from 2012: https://lkml.org/lkml/2012/12/23/75 And it is his kernel so it is his rules. John Johansen admitted he messed up ( http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02539.html ) and promised to handle things better in the future so all is well.
"Linus has made it incredibly damn clear what "no user space regressions ever" mean." Absolute shame he doesn't even know the basic definition of 'regression' and uses the word incorrectly in every way. Breaking shit is simply breaking shit. It's not a regression unless something was broken first, then fixed, then the SAME ISSUE comes back in a later code change.
According to Linus: THE KERNEL NOT GIVING THE SAME END RESULT WITH THE SAME USER SPACE
According to Wikipedia: A software regression is a software bug that makes a feature stop functioning as intended after a certain event (for example, a system upgrade, system patching or a change to daylight saving time).
Seems like the two definitions are similar. There's no requirement that the defect be one that was seen earlier, fixed, and then reappears.
Re: A regression is the kernel not giving the same result with the same user space
#189John Johansen will survive. Linus has made it incredibly damn clear what "no user space regressions ever" mean. See f.e the similar rant from 2012: https://lkml.org/lkml/2012/12/23/75 And it is his kernel so it is his rules. John Johansen admitted he messed up ( http://lkml.iu.edu/hypermail/linux/kernel/1710.3/02539.html ) and promised to handle things better in the future so all is well.
> Linus has made it incredibly damn clear what "no user space regressions ever" mean out of curiosity, how does a policy like this translate to microkernel OSes (e.g. Redox) where most everything runs in userspace?
Re: A regression is the kernel not giving the same result with the same user space
#190Earlier quoted context omitted.
> John Johansen will survive. We really need to stop excusing Linus's behaviour. Just because we may happen to agree with what he is saying doesn't mean we also have to agree with how he is saying it.
Disagree. It seems like Linus’ acerbic and direct means of communicating is the only thing keeping garbage code out of the kernel. He’s also made his views on “why not be nicer” well known. People need to get over it - his project, his rules. Plenty of other projects out there to hack on if getting yelled at when you disengage your brain is too much. Most of which don’t have the obsession with not breaking stuff for…
Linus is no role model. His imprecations are not what make Linux work.