3K Lines Of New Rust Infrastructure Code Head Into Linux 6.13

[microcode]

This is a pointless article IMO. Just made to advertise Rust. But at least we got another monthly article where we can argue about which language is better

So is it pointless or did you just tell us the point?

[Britoid]

It's a meme response format. FTFY = Fixed That For You



My point is that, if running Linux on Apple Silicon is a toy because it's designed for macOS and Apple doesn't officially support it, then running Linux is also a toy on motherboards from vendors like Gigabyte which are designed for Windows, whose support reps will say "Linux is the problem. Our board isn't buggy/broken/whatever. Switch to Windows." if you don't lie about running Windows when reporting firmware bugs that also affect Windows.

Completely different, the components of the board and the chip set itself are officially supported under Linux by the respective OEMs

Chipset = AMD/Intel
CPU = AMD/Intel
GPU = AMD, Intel (lol), Nvidia
Disk Storage = OS neutral protocols
RAM = Ditto above
USB = Intel/AMD

The UEFI specification also provides a OS-neutral interface for software to talk to the hardware.

Apple does none of this for Linux

Apple can distribute a automatic firmware update tomorrow and break the Apple Linux GPU driver, none of the GPU specification is open, nor is it supported by Apple in anyway, thus its a toy that can break at any time.

[Weasel]

I assume you spell "color" as "colour". I know that because you spelled it "civilised". It's spelled "civilized". If you were civilized you'd know that. Well, technically, "it's" is spelled "it's".

Yeah it's called British English.

What did I expect from a rust fanboy other than ignorance?

[skeevy420]

Vorpal It might not be the "civilised" conversation you wanted, but it's the "civilized" conversation you got

Ironic that it, too, isn't very civili$ed

[skeevy420]

Yeah it's called British English.

What did I expect from a rust fanboy other than ignorance?

Y'all aren't getting the Dad joke

[skeevy420]

So is it pointless or did you just tell us the point?

Two pointlessnesses don't make a point

OR

I make two points in the morning
In the car I make two points

[mobadboy]

Michael Larabel adjusted his chair. The clock ticked toward 8:13 AM, the sacred hour when late-breaking news hit Phoronix headquarters (his home office). His fingers hovered over the refresh button on the mailing lists he religiously tracked. And then, like a thunderclap in an alpine forest, it arrived.

A pull request. A BIG one.

Michael’s eyes squinted at the screen, his heart skipping as he processed the subject line: "[GIT PULL] Rust for 6.13."

Three thousand lines of Rust. It was enough to drive the Phoronix server analytics to unprecedented heights. His head swam. He leaned back in his chair and exhaled, sweat already forming on his brow.

"Ach du lieber Himmel," he muttered in reverence, his voice tinged with disbelief. He fumbled for his bottle of Köstritzer Schwarzbier, his favorite German beer, because of course it was—dark, rich, and utterly dependable, just like his years covering open source.

The beer stood ready, condensation forming around its base. Not yet, old friend, Michael thought. First, the work must be done.

He opened his text editor and began typing at lightning speed. His fingers danced over the keys with a grace borne of decades in the trenches of FOSS journalism.

"Overnight the Rust for Linux lead developer Miguel Ojeda submitted the big set of Rust infrastructure/toolchain updates for the Linux 6.13 holiday kernel." he wrote, the words spilling out effortlessly.

He could hear them already—the clickbait warriors, the armchair experts, the various factions sharpening their rhetorical blades. The Rustaceans would proclaim victory. The C diehards would lament the purity of the Kernel being tainted. And Michael? Michael would soak it all in.

An hour later, the article was published. He leaned back and cracked open his Schwarzbier, the sound of the cap releasing like a fanfare for a job well done. He took a long, satisfying sip. The bitterness complemented the sweetness of success.

Michael checked the server stats. Hits were already spiking. Comments were rolling in, full of flame wars and unnecessary vitriol. Perfect.

He wiped the sweat from his brow and smiled. It was a good day. No, a great day.

He raised his bottle to the screen. "To Rust, to the Kernel, and to the morons who argue about it."

The day was young. And tomorrow? Tomorrow, another pull request might just bring him more joy.

[Quackdoc]

Which part or subsystem of the Linux kernel would like the most to see adopt Rust?

Is it graphics device drivers? or the network stack? or is it file systems? ext4 or Btrfs or a brand-new one? Perhaps the CPU scheduler or the I/O scheduler?

I'm not sure if any subsystem specific people want rust so to speak, but I know various developers do, Obviously google want's as much of it to be rust as possible, as they have almost explicitly stated with their binder PR. Obviously we are starting to see some gpu stuff in rust too with asahi, for file systems we have seen a couple POC rust file systems either EXT2 re-implementation and erofs rustification, as well as puzzleFS and kent has stated multiple times he want's rust for bcachefs. IIRC there were some networking drivers in rust too.

So it's less of what subsystem would like to adopt rust, and more of, what devs specifically want to, because they are spread out

[kpedersen]

Separately, Christian Brauner sent in the this pull request today with the Rust language bindings for the PID namespaces. These Rust bindings in turn are needed by various Rust kernel drivers that are forthcoming.

More bindings to stagnate and rot as interfaces inevitably change.

For people who believe bindgen/SWIG is as effective as C++'s direct interop with C, perhaps ask yourself why these bindings are needing to be hand written / maintained rather than just churned out by bindgen/SWIG.

[Old Grouch]

I assume you spell "color" as "colour". I know that because you spelled it "civilised". It's spelled "civilized". If you were civilized you'd know that. Well, technically, "it's" is spelled "it's".

Well, civilized comes from a Latin root - civis ("citizen"), and the historical rule is that words with a Greek root end in -ize, whereas those with a French or Latin root end in -ise. That said, English changes, and contemporary usage varies by country. Which is the more civilised is a debatable point.