As soon as he's not in charge quality is going to go right to shit though.
this post was submitted on 10 Aug 2025
345 points (98.9% liked)
Tech
1884 readers
110 users here now
A community for high quality news and discussion around technological advancements and changes
Things that fit:
- New tech releases
- Major tech changes
- Major milestones for tech
- Major tech news such as data breaches, discontinuation
Things that don't fit
- Minor app updates
- Government legislation
- Company news
- Opinion pieces
founded 2 years ago
MODERATORS
He has taken several months-long breaks and things have been fine. There are other trustworthy devs (like Greg Kroah-Hartman) who he leaves in charge who do just fine at holding the line in his absence. They might not publicly shame bad pull requests as elegantly as Torvolds, but the kernel will probably be fine.
That my worry too.
Linus needs to be the first person whose brain is uploaded to a computer. He is simply too precious to lose.
That technology should run Linux. For stability.
load more comments
(1 replies)
Honestly that's pretty tame given his history
Which is a fairly shocking thing to say really. I thought promised to be less of a dick a while ago. Guess he couldn't keep it up.
Spicy Linus > mild Linus.
This is 2*
It is much less dickish that what he used to say, so he's keeping his promise.
From Google? Probably vibe-coded crap.
Holy shit. Torvalds is only 55 and that's what he looks like now?
Holy fuck.
Now, I would hope there's no garbage inside the RISC-V parts, but that's your choice. But things in generic headers do not get polluted by crazy stuff.
So can anyone explain this? What are header files in this context and why are unnecessary functions especially problematic for them? Why would it not be up to Linus or not his concern what is included in the "RISC-V parts"? I guess this is all code for a Linux kernel that is built on top of RISC-V which I think is an assembly language, and not a modification to RISC-V itself?
I get the logic about make_u32_from_two_u16() being bad at least.
A header file in the C family of programming languages contains the declarations for each function that gets defined in the accompanying code file. Ideally, the header file should only contain import statements, some basic definitions, and function declarations. It should not contain any actual executable code.
A header file basically exists to tell the compiler "hey, these functions exist in this file, don't freak out if it gets called before you see its definition." Without the header file, you'd need to write the declarations at the beginning of the code file (in the header, hence the name).
load more comments
(6 replies)
Palmer Dabbelt took it like a champ though:
OK, sorry. I've been dropping the ball lately and it kind of piled up as taking a bunch of stuff late, but that just leads to me making mistakes. So I'll stop being late, and hopefully that helps with the quality issues.
view more: next ›