I feel like the comments are taking away the wrong message from this. He used it to do the part of the project that he has poor knowledge/experience/capacity for. He needs a visualization but the project isn't about visualization. He's spent a lifetime coding in C, not writing python-based visualizations.
There's a big difference between vibe-coding an entire project and having an AI build a component that you lack competency for. That is what is happening here.
It's the same principle as a startup that builds it core functionality itself in-house and then uses off-the-shelf libraries for all the other uninteresting details.
>Add README and LICENSE file
I'm pushing it out to github not because it needs to be public, but
because of my policy of using the internet as my backups. And because
it makes it so much easier to just sync between machines.
Very cool to see a legends side project. I'll check this out when I have time even though I can't understand C well.
What's truly "sad" is that it's ok if Google does it. It's apparently not ok when OpenAI, Musk, etc do literally the same thing.
This whole controversy reminds me of that Rhodesian designed shotgun marketed as "Street Sweeper" in the US. Making a tool is one thing. Brandishing its unsafe working end to potential customers in an attempt to impress them, alas, could lead to interesting situations...
Depends on stage. Codex/Claude-generated code have hinting and doc strings, and will gladly add tests for every change you're doing. (That's why vibe coded projects have a gazillion tests.)
I feel like the comments are taking away the wrong message from this. He used it to do the part of the project that he has poor knowledge/experience/capacity for. He needs a visualization but the project isn't about visualization. He's spent a lifetime coding in C, not writing python-based visualizations.
There's a big difference between vibe-coding an entire project and having an AI build a component that you lack competency for. That is what is happening here.
It's the same principle as a startup that builds it core functionality itself in-house and then uses off-the-shelf libraries for all the other uninteresting details.
>Add README and LICENSE file I'm pushing it out to github not because it needs to be public, but because of my policy of using the internet as my backups. And because it makes it so much easier to just sync between machines.
Very cool to see a legends side project. I'll check this out when I have time even though I can't understand C well.
Which is exactly what he said before https://youtu.be/mfv0V1SxbNA?t=764
BassForLinus.mp3 ?
I never clicked a file so fast in my life before.
It's a tame bass sample sound. Probably from Linus himself. I want more!
https://github.com/torvalds/AudioNoise/blob/main/BassForLinu...
Is he slapping at 00:53? Can't wait til Davie504's cover.
That is truly sad :-(
What's truly "sad" is that it's ok if Google does it. It's apparently not ok when OpenAI, Musk, etc do literally the same thing.
This whole controversy reminds me of that Rhodesian designed shotgun marketed as "Street Sweeper" in the US. Making a tool is one thing. Brandishing its unsafe working end to potential customers in an attempt to impress them, alas, could lead to interesting situations...
Why is that?
Depends.
This is on projects that are not serious. So I will treat it as such.
You should worry if vibe-coders submit patches to the Linux Kernel and they do not understand them.
It's official, vibe coding is legit.
No it’s not, there are so many issues yet to be solved. Privacy, responsibility, etc. It literally says nothing for prototyping, we have all done it.
it's always been.
You mean you want it to be.
I use it daily and it just works. If you haven't found your agentic workflow or you don't prompt it well, that's not an ecosystem problem.
That is my point it’s a you thing. Maybe your QC are lower than mine? I don’t know. No one else on my team uses it for that reason alone.
No tests, mypy type hinting or doc strings -- just pure vibes
Depends on stage. Codex/Claude-generated code have hinting and doc strings, and will gladly add tests for every change you're doing. (That's why vibe coded projects have a gazillion tests.)
I wa referring to linus' script in the repo