Yeah, it just doesn’t make sense!

So lore-wise it’s not supposed to be possible, but that one room does indeed have moving portals. The explanation is supposedly that portals disappear when the object they are on is accelerated.

Granted. The portals immediately close when you try to move the plates.

Good. This dev has explicitly said that he has non-technical reservations, and that he’ll abuse his position to get his view pushed through.

I hope they can keep themselves from doing the same for the rest of the systems they’re maintaining.

I got that, but I don’t think it’s true. Humans don’t provide them with food (except during winter, but that’s also more recent), we prevent escape. Otherwise why are pens necessary? We’d just pile up food, and the animals would keep coming back.

I’m not sure that’s accurate. They’d leave if they have no access to grass, but you don’t have to actively give it to them for them to stay.

For predators generally yes, but for prey not necessarily

It does take a while

To get used to the INTOnation

But once you’ve managed that

The man is pure gold

And as always:

🎶 eeeenjooooyyyyy 🎶

Oh, he just had that lying around

Extrapolating from the slipperiness of lube on the floor: this is a terrible idea. People will be bouncing around like pinballs.

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.

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.

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.

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.

Linus should have stepped in earlier. The R4L guys have been running against walls over and over (just look at how T’so, the “thin blue line” guy, spewed hate at that one conference), because individual developers think they can use their power to slow down the R4L project. They don’t argue on a technical level. Linus, as the project lead, has to step in when this happens, otherwise the experiment can’t work.

That now involves fixing Rust drivers, so you’re going to need to know Rust.

The R4L approach is that C maintainers never need to touch any Rust code. They can break it all day long without paying any attention to it. This has been an essential part of the project from the start, I don’t understand how people talking about this topic still don’t understand this.

Just like the ocean is the best body of water for children who want to learn about swimming

Though still far easier than a calzone

Why? I’m happy to support the developer of an application I use (as long as he actually uses the funds to fund further development).

I’ll give you the benefit of the doubt and explain it, if you’re actually not understanding it.

Sync is a freemium app. You can use it for free, but you will have ads and tracking. Or you can pay a one-time fee to upgrade to premium, which removes ads and trackers. This upgrade costs 20€.