Linux
Welcome to c/linux!
Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!
Rules:
-
Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.
-
Be respectful: Treat fellow community members with respect and courtesy.
-
Quality over quantity: Share informative and thought-provoking content.
-
No spam or self-promotion: Avoid excessive self-promotion or spamming.
-
No NSFW adult content
-
Follow general lemmy guidelines.
view the rest of the comments
Hey at least he just came out and said it. No overly-sanitized corporate lingo statement, just "eh, I was wrong, so let's figure out how to improve this process".
What's the big deal?
Linus has shut down criticism of LLM generated code in the kernel and now it's causing problems, as many people pointed out it would. Linus allowed and encouraged this and now he's upset about the bed he made.
Linus is very outspoken about his opinions. That should come as no surprise.
That said, I don't necessarily disagree with him here. There are far too many people who, at any mention of AI involvement with a codebase, immediately scream "SLOP" and "VIBECODED" without even trying to consider how it was used. And yes, there is no shortage of idiots who vibecode absolute slop, but there are also plenty of very talented devs who use it as just another tool in their toolbox, so to speak, and those are the people who will ensure they understand the code and make sure it works like it's supposed to before committing.