this post was submitted on 13 Feb 2025
322 points (97.6% liked)

Linux

50400 readers
876 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] arisunz@lemmy.blahaj.zone 33 points 1 week ago (2 children)

why they feel it’s Linus’ responsibility to make Rust happen in the kernel

who does? are you talking about marcan? because as far as i can see, what they're asking for is for linus to make a stance and actually say whether R4L is a thing they want or not. because linus' attitude so far has been "let's wait and see" which hasn't been all that helpful, as said in the blog post.

[–] PetteriPano@lemmy.world 24 points 1 week ago (1 children)
[–] arisunz@lemmy.blahaj.zone 10 points 1 week ago

aughhhhhh here's your upvote. git out.

[–] vanderbilt@lemmy.world 12 points 1 week ago (2 children)

Ultimately Linus’ opinion here does not matter in the positive. He can say Rust in kernel is good, but that does not summon the skill and work to make it happen. He can say it’s bad and quash it, at the potential expense of Linux’s future. His position of avoiding an extreme is a pragmatic one. “Let them come if they may, and if they do not it was less a loss for us.”

[–] arisunz@lemmy.blahaj.zone 18 points 1 week ago

see, i could maybe agree with this if it weren't for the amazing work from R4L that already has been and continues to be done, despite subsystems maintainers putting their foot down and going "Not In My Back Yard, bucko!". how many more maintainers does R4L have to lose before Linus realizes he might need to take a stance as a project lead?

[–] JuxtaposedJaguar@lemmy.ml 1 points 1 week ago

Linus can merge whatever patches he wants to, and the stonewalling subsystem maintainers would have to deal with it--like he did with the eBPF scheduler. R4L maintainers already wrote the patches, they literally just needed to be merged.