If we are going to be honest, let’s not be misleading.
Nobody is looking to replace C in the kernel just to switch out the language. This is not a “rewrite it in Rust” initiative.
What the R4L folks want is to be able to write “new” code in Rust and for that code to call into the C parts of the kernel in an idiomatic way (idiomatic for Rust). So they need to create Rust interfaces (which they, the R4L side, are doing). This whole controversy is over such an example.
At this point, we are talking about platform specific drivers.
Now, new kernel code is written all the time. Sometimes newer designs replace older code that did something similar. So yes, in the future, that new code may be written in Rust and replace older code that was written in C. This will be a better design replacing an inferior one, not a language rewrite for its own sake.
Core kernel code is not getting written in Rust for a while though I do not think. For one thing, Rust does not have broad enough architecture support (platforms). Perhaps if a Rust compiler as part of GCC reaches maturity, we could start to see Rust in the core.
That is not what is being talked about right now though. So, it is not a reasonable objection to current activity.
Linus is pro-Rust. It is not clear from what you wrote that you realize that. He has merged plenty of Rust code. I personally expect him to merge the change that caused all this current drama (though I could clearly be wrong about that).
Right or wrong, this is how Linux kernel dev has always worked. How long did it take for real time to get in? How smoothly is the bcachefs merge going? Have you read any of the GPU driver chatter?
Honestly though, it is not just the kernel. How much different is the Wayland scene?
I am hardly defending Linux here by the way. I think the maintainers are blocking progress. I am merely pointing out that it is hardly new or unique.
Anyway, RedoxOS is quite progressive. They would probably love help from anybody that finds Linux kernel dev too stodgy.
Stop sending the US oil. Stop sending natural gas. Stop sending electricity. Stop sending steel and aluminum. Stop sending them rare earths. Stop sending them wood. Do it immediately. Do it now.
We will see who needs who.
Yes, this would cause economic pain in Canada. So will not doing it.
Everything above is in demand all over the world.
Frankly, every other county should attend a summit next month where we ALL agree to stop sending the US anything and stop buying anything from the US.
If America wants to isolate themselves, I say let’s go!!
The build quality may not be that good but the technology and the designs are excellent. I say that as somebody that does not use macOS (well, not much).
As somebody that buys older hardware, I cannot wait to use Linux on Apple Silicon in a year or two. When I do, I will be immensely appreciative of all the effort that is going into it now. It will feel pretty open to me by that point.
Most importantly though, people put effort into the things that they want to. I am thankful that they have that freedom.
I am with you on that last line. However, I remain more hopeful.
As long as Linus keeps merging code, Rust will eventually win. And by win I just mean that it will overcome the haters sufficiently to render their resistance futile.
There is only so much support infrastructure needed before large chunks of Rust can be committed ( at least on the driver side ). We are not so far away from that. Once real code starts to appear the “show me” will drive adoption elsewhere.
Take this case, it all started over a bit of code. The subsystem maintainer refuses to take it. But it does not require any changes to existing code. It just has to be merged.
Linus can take it directly. If he does that, the Rust folks can start to use it. The sub-system maintainer will lose in the end.
At some point, the battle will be lost by those trying to block Rust.
Forget tariffs. Strop sending him oil and electricity. Completely. Immediately.
Hold a press conference that all the comedians will cover.
Or even just stop sending ANY aluminum or steel. They cannot just replace it easily. Their economy would skip the tracks. If you don’t want to stop sending it, put a 50% export tariff on before it even gets to them.
People will notice that.
I feel like Canadians would back our government and Americans would not.
It would all be over in our favour fairly quickly.
Absolutely solid retort that totally addresses what I said on the merits. Also, way to nail the tone. Both hallmarks in debate from people that know they are right.
For anybody reading from the sidelines, most of the “TNT” in my analogy comes from the fact that the Manjaro repos are incompatible with the AUR.
Read both comments and decide for yourself what advice to take. I have offered my warning but do not wish to battle about it.
The cynicism is well deserved. They have been on 2.99 for years.
That said, I have been using 3.0RC1 for a bit. It ships packaged with my current distro and has worked well for me. This release should be quite usable even though 3.0 has not officially shipped.
Where I live, that seems like a truly terrible idea.
Cyclists move really quickly and are somewhat reckless and selfish as they try to maintain their speed and momentum in traffic. It barely works with cars despite the dedicated lanes. It always causes problems anywhere that bike and pedestrian traffic meets, especially in areas n like temporarily diversion or construction.
I support bike lanes and, for quite a while, I use them extensively biking from the suburbs to my work downtown. I was probably the same.
We should not place slow-moving ( and vulnerable ) traffic in the path of cyclists. We do not need grandma or a paraplegic getting wiped out by a 180 pound guy going 25 km an hour.
You could try to make the bike lane massively wider. This would be a poor use of space. It would greatly increase congestion and the “slow alternative vehicle lane” would be almost empty all the time. It would be 30 empty wheelchair parking spots at the mall while cars get in accidents trying to find a spot but worse.
Of course, out of the city, things are different. My family enjoys a nice bike ride every Sunday on a local road that has quite a wide lane running side it that pedestrians, wheelchairs, scooters, and cyclists share. The lane is wide enough and traffic density is low enough. There are no buildings to move so, the “road” got wider with the extra lane rather than space for cars being reduced.
Manjaro is like a nice car with a canister of TNT attached to it. At first, all you experience is the nice car. If you really like the car, it is easily to feel smarter than the guy who warned you not to drive it. As time goes on, the chances that the TNT explodes goes up. However, it is always possible that your roads are smooth enough that it never blows up for you. Regardless, if you know about the design flaw, recommending such a car to others is really, really bad advice.
Using the AUR with Manjaro is like driving the car above on a gravel road. It does not guarantee that the TNT will go off, but it makes it much more likely.
I hope Manjaro continues to work well for you. Truly.
Sounds like you two agree