FooBarrington

Because I am familiar with human behaviour.

Human behavior doesn't dictate that a Linux kernel with failing Rust builds wouldn't get published.

I’m not too familiar with Linux’s CI system but I assume they at least test that it compiles, even if it is disabled by default.

Yes, the systems would notice that something broke. Those systems have no say in whether something gets released.

Only the average temperature of the parts close to the surface, which is why the surface area is so important.

But by reducing the albedo the air gets warmer, which makes the ice melt faster.

No, I'm not trying to tell you that. I thought I was pretty explicit?

You keep taking small parts of what I'm saying, and misconstrue them to be completely different arguments. Why don't you just listen to my actual words?

Thanks for the recommendation, I'll give it a try!

I think it would decelerate, as there's less surface area.

Not that it matters, since the temperature is affected by the ice going away, so it's an impossible scenario anyways.

Okay? And why are you imagining things would go down like that, when the policy is specifically not doing it this way? When this issue hasn't occurred so far?

Rust is disabled by default, so it's not like it would be harder to build a kernel when it's broken. Seriously, I just don't get why you're imagining these things.

Sadly not, I'd also be interested in one!

I very much dislike Mozilla's direction over the last decade. They're introducing user-hostile features that subtly break normal browsing experience, even when disabled[0]. Not like Google is better, but I'm also trying to get away from Mozilla.

[0] On Firefox Mobile, there's a "feature" which makes the address bar auto-complete domains of companies paying Mozilla. I noticed this with Netflix - I never visit, but when I start writing a URL with n, roughly every 10th time Netflix was suggested. You can disable this feature, but this doesn't actually disable it. The address bar no longer auto-completes with Netflix, instead it just doesn't autocomplete! So 9/10 times I can write n and press Enter, but 1/10 times I press n and search for the letter n.

Mozilla doesn't care whether they break features, as long as they can make more money. I strongly dislike this approach by the supposedly "good" browser manufacturer.

It's not petty to expect depth when depth is promised, but even shallow depth would have been enough. I'd have been happy with a voiceline by the clerk who sold me the apartment. I'd have expected an animation, but a voiceline would already make it feel alive. But there's not even that! You press the button and own the new apartment, and that's it.

That's not "alive", that's deader than the average game from 2005.

Oh and by the way, can you point me to a single action rpg game that allows you to redecorate your place?

Fallout 4? Fallout 76? Starfield?

You might notice I didn't say "Cyberpunk 2077 is shit because I can't redecorate my apartment", but it's ridiculous to act like NO GAME EVER has allowed you to do that. Bethesda games have allowed you to do that, even though they are shit.

What's there not to believe? If Rust gets broken, either someone will fix it, or the kernel releases with broken Rust. Where's the issue?

It's such a strange position to take.

Thanks!

I'm not trying to assign blame for Marcan's burnout, but it's important to try and understand what went wrong here, because things did go wrong. Linus's earlier inaction (I haven't seen anything about reaching out privately, could you link that?) isn't the cause of it, but it's what should have prevented things from going this far.

If we ignore what went wrong, the same thing will happen again.