It’s difficult

Goodbye

If you tell most linux developers to gtfo, then whatever is developed by the ones who are left is not mainline linux.

Yes, this is like not checking an error code.

You can do that in C, too.

Now that’s a conspiracy theory.

So you want to force C programmers to write Rust or GTFO.

Java was invented 20 years sooner.

Linux is a development ecosystem. If everyone agrees to switch to Rust it can switch to Rust with continuity. But they won’t.

Wouldn’t it still crash when the smart constructor was called?

The bindings cause maintainability issues. That’s the problem.

Linus and GKH, if they merge something that breaks every time C programmers change a kernel API

The only compromise Rust programmers would accept is C programmers learn Rust so when they break Rust code they can fix it.

So what’s the solution that doesn’t involve C programmers writing Rust?

They said it wasn’t going to happen but their plan will result in it happening, how do you square that?

If you write unsafe code then how should it compile?

“There’s no compromise, I’M RIGHT AND YOU’RE WRONG!”

no wonder everyone hates rustphiles

When did they refuse to share knowledge?

You can, but you can’t turn a 30 year project on a dime. They’re understandably frustrated that newcomers keep coming and screaming RUST RUST RUST RUST RUST

How many vulnerabilities have the kernel Rust team introduced in the same time period on the same code?