He talks of a new memory safe kernel disrupting Linux the way Linux disrupted others. Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. It's caused a lot of trouble so far and for what? The dev community is fractured and infighting is rampant.
> Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place.
Can you clarify these two sentences? You say there should be a memory-safe kernel, and then you say Rust should never have been allowed, which is the opposite.
He talks of a new memory safe kernel disrupting Linux the way Linux disrupted others. Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. It's caused a lot of trouble so far and for what? The dev community is fractured and infighting is rampant.
> Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. Can you clarify these two sentences? You say there should be a memory-safe kernel, and then you say Rust should never have been allowed, which is the opposite.
That memory safe kernel doesn't necessarily have to be Linux itself.
He talks of a new memory safe kernel disrupting Linux the way Linux disrupted others. Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. It's caused a lot of trouble so far and for what? The dev community is fractured and infighting is rampant.
> Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. Can you clarify these two sentences? You say there should be a memory-safe kernel, and then you say Rust should never have been allowed, which is the opposite.
He talks of a new memory safe kernel disrupting Linux the way Linux disrupted others. Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. It's caused a lot of trouble so far and for what? The dev community is fractured and infighting is rampant.
> Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. Can you clarify these two sentences? You say there should be a memory-safe kernel, and then you say Rust should never have been allowed, which is the opposite.
> He talks of a new memory safe kernel disrupting Linux the way Linux disrupted others.
So the next paragraph means:
> Maybe rust should have never been allowed in the [Linux] kernel in the first place.
> Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. Can you clarify these two sentences? You say there should be a memory-safe kernel, and then you say Rust should never have been allowed, which is the opposite.
That memory safe kernel doesn't necessarily have to be Linux itself.
Same opinion here, have all this giant proRust energy and put it behind a few Rust kernels, combining the Rust super powers with latest kernels architectures and have at least one Rust kernel that is not UNIX but something super modern.
He talks of a new memory safe kernel disrupting Linux the way Linux disrupted others. Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. It's caused a lot of trouble so far and for what? The dev community is fractured and infighting is rampant.
> It's caused a lot of trouble so far and for what? The "for what" seems pretty obvious, no? It's the same reason you would use Rust over C in any other project. Memory safety and more modern PL features.
In my opinion, in the case of the Linux kernel, Zig (once it reaches 1.0) would be a much better, more natural, and less painful choice than Rust.
He talks of a new memory safe kernel disrupting Linux the way Linux disrupted others. Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. It's caused a lot of trouble so far and for what? The dev community is fractured and infighting is rampant.
> Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. Can you clarify these two sentences? You say there should be a memory-safe kernel, and then you say Rust should never have been allowed, which is the opposite.
What they're getting at is that it probably would have been better if the Rust people had started their own kernel project, cherry-picked the pieces of Linux they wanted, and then made their own new thing without three decades of obsolete Unix/Linux baggage. This would mean they could spend their time actually writing software and and less time trying to convince a bunch of C programmers that their time is at an end and their influence is counterproductive.
He talks of a new memory safe kernel disrupting Linux the way Linux disrupted others. Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. It's caused a lot of trouble so far and for what? The dev community is fractured and infighting is rampant.
> Well, maybe that's exactly what should happen. Maybe rust should have never been allowed in the kernel in the first place. Can you clarify these two sentences? You say there should be a memory-safe kernel, and then you say Rust should never have been allowed, which is the opposite.
Meaning: Maybe there should be a competitor to Linux written in Rust
BTW: There are a few Rust OS kernels, but none of those have the popularity of Linux of course.
I lack context. What is the “constant nontechnical nonsense”?
https://news.ycombinator.com/item?id=41386939 A comment there has a link to a video of what seems to be the final straw.
Also linked in the email in the GP.
> Lastly, I'll leave a small, 3min 30s, sample for context here:
https://youtu.be/WiPp9YEBV0Q?t=1529 -- and to reiterate, no one is trying force
anyone else to learn Rust nor prevent refactorings of C code.