Literally no one is forcing you to switch. Just keep using coreutils.

Can I at least get some sleep please? Jeez... How many more fires I will have to put out this week?

What. The. Fuck.

Amazing

Chris Sawyer really went off the deep end after programming RCT in assembly.

https://youtube.com/watch?v=IrVA1BBHFHw&ra=m

Oh, sorry, I couldn’t hear you over this BITCHING ROLLER COASTER BUILT IN EXCEL

I got sent an excel file with a full volumetric heat diffusion simulation once, and it was most impressive thing until I heard about this roller coaster

At least it sounds like the 9.0 ones only affect systems that are running SMB Direct, which sounds like a pretty niche setup

> "sounds like someone trying to push their preferred language onto others."

> didn't even name Rust in the first comment

I literally only talked about Rust when someone else mentioned it, because I'm not specifically talking about Rust.

Whereas yes, Rust is relevant to the Linux kernel for obvious reasons (matching C's speed and being easily interoperable with it), I said "a modern language" because I'm talking generally about the use of old, unsafe languages and major exploits surrounding problems that modern languages fix cropping up every 5 seconds.

I'm not going to police my own tone about what are clearly negligent engineering practices. SWE should be treated with the same level of scrutiny as other engineering fields when its poor, outdated practices are constantly causing accelerating worldwide damage.

"Quit complaining about fixable systemic issues unless you're able to personally go fix them yourself. Bridges collapsing due to negligent engineering practices? Go survey and fix them yourself. I am very smart."

I mean yes, I do, given safe Rust inherently fixes seemingly every exploit listed in this article:

• RCE from integer overflow (not possible by default in Rust, CVSS 9.0)
• RCE from a race condition (not possible in safe Rust, CVSS 9.0)
• An exploit of a buffer copy
• An out-of-bounds write leading to local privilege escalation
• Using an uninitialized resource
• TCP query stack buffer overflow leading to local privilege escalation

I feel like it's the 1960s and I'm being told "we get it, you like seatbelts".

Edit: Sorry, re: the first one. I was misremembering based on a mix of a few things (see below). It does this in debug mode (which in itself is good to have), and it won't compile if it can detect an overflow statically, but it's not checking over/underflow at runtime by default. It can do this if you want it to, but that's an inherent speed penalty from C. I was thinking of Swift, which does automatically detect integer under/overflow at runtime unless you explicitly tell it not to on a per-operator basis.

In the spirit of not making you "trust me bro" since I was so wrong about the integer under/overflow one, here's Rust's overview of how safe Rust guarantees against data races.

I only program in Excel conditional statements and I never get these vulnerabilities.

Excel is therefore proven the most secure coding language, and like a Swiss pocket knife it doubles as an industrial grade database.

(pats hood) Listen to that xls(x) purrr..

Oh no sorry I can't show you right now, I had to open my spreadsheet so it'll be a few hours til I can start work.

Yes, we get it, you like rust.

SMB Direct remote code execution vulnerability due to integer underflow.

It's a day ending in 'y' and we've found another RCE that wouldn't exist in a modern language designed to catch things like integer under/overflow.

I think disclosure is accepting the premise that it is something that needs to be disclosed.

Programmers don't typically list the entire suite of software that they use to make programs in their commit messages. AI isn't anything special, it's just the latest applicable technology.

"But the Environment, Data Centers, My Dreams of a Graphics Card, Capitalism makes AI suck, Clankers, etc"

Yes, the way that AI is distributed in the West and the investment in that system is incredibly bad for everyone but the people profiting off of it. I don't think that you should use OpenAI, Anthropic, etc as it supports this destructive process that will likely result in some kind of mass financial collapse at some point in the near future. I'm anti-AI in that sense, I also think that this is a separate issue than the actual technology which is available in many forms that are not sourced from that destructive system.

That being said, I think that you should not use Microsoft products as it supports a company that provides the computer infrastructure which supports Israel's genocide of Palestinians.

I also think that it isn't any of my business if the developers of the Linux kernel pay for and use Microsoft's Visual Studio on Microsoft's Windows 11. Just like I don't think it's any of my business if a kernel dev uses Claude Code, or VS Code with local AI.

This expectation that they need to 'disclose' it doesn't provide any utility for the Linux project and, instead, serves to paint a target on themselves for the extreme parts of the anti-AI crowd to dogpile and harass.

It was the right decision.

e: Also, it provided free advertising for AI companies.

IDK but I have a lot of issues with that list anyway... they seem to have a strange definition of "permissive AI policy", i.e. any mere mention of an AI service gets you on the list.

Example: OpenBSD and NetBSD both show as "permissive" on the list, even though both have publicly stated otherwise, just because there are one or two commits where someone (prominent dev) commented something like "I had help from Claude but you can't tell, and I personally vouch for this and I know what I'm doing."

Rejection of tools and disclosure of tool usage are two different things.

That being said, there's much more faith in those contributing to the Linux kernel than in any other organization I've met.

It was a unanimous decision by the kernel maintainers at the 8 October summit.

If you want to read Linus' take, this is his comment in the thread discussing the topic: https://lore.kernel.org/all/CAHk-=whTs09_ozN+e09GU68N1wPP56MUzDjrg9rnKxQUa0A_4Q@mail.gmail.com/

The hivemind, aka a social media bubble.

Pretty sure most users of Linux are not part of that and are going to keep on using Linux.

Edit: looks like the Fediverse instance this community is running on is using tainted code by the definitions used in your link. Will this ship also be jumped?

I think the hivemind has already spoken, they are taking this to mean that the kernel is now vibe-coded and people are actively jumping ship.

According to the article imecth linked to in another comment it was already essentially meaningless.

This ain't gonna end well.

Open source when someone forks something for a reason that aligns with my worldview: "The beauty of open source! Anyone can fix a problem!"

Open source when someone forks something for a reason that doesn't align with my worldview:

I see, thanks for an explanation

I am afraid IoT would ignore expiry date if it bakes certificates in like they already do sometimes