Looks like he’s just toying around with it in some project. Why would he take other’s words for it when he can just test it himself? Try it out, see what happens, draw conclusions.
There’s a lot of mindless hype and a lot of mindless hate around these tools. Makes sense to try these tools and form your own opinion
Didn’t he daily a M series macbook when they came out?
I don’t remember people being obnoxious about that
AI can be a useful tool.
AI is fine when it is your hands. Not when it is your brain. As long as you can vet it it can be useful for coding. Its the moment we give agency away to the AI that many see issues with it.
The problem is that AI is not useless. It has a lot of other issues, but not that it is never a helpful tool.
With constrained data sets it’s actually really useful.
Parsing text and logs and correlating events, super useful.
When you dump all human “intelligence” into it you discover how dumb we are collectively.
Just in case it slipped your eyes when you saw “Torvalds”: this is not about the Linux kernel.
From the project’s README:
Also note that the python visualizer tool has been basically written by vibe-coding. I know more about analog filters – and that’s not saying much – than I do about python. It started out as my typical “google and do the monkey-see-monkey-do” kind of programming, but then I cut out the middle-man – me – and just used Google Antigravity to do the audio sample visualizer.
This is the commit: https://github.com/torvalds/AudioNoise/commit/93a72563cba609a414297b558cb46ddd3ce9d6b5
Tbf it’s his project so he can do whatever he wants
Issue is when people do things like that one dude who had Claude implement support for DWARF in… Whatever language it was (Something MLy I think?) and literally didn’t even remove the copyright attribution to some random 3rd person that Claude added. It was a PR of several thousand lines, all AI generated and he had no idea how it worked, but said it’s ok, Claude understands it. He didn’t even tell anyone he was going to be working on it so there was no discussion of the architecture beforehand.
Edit: Ocaml. So I was right that it was something MLy lol
Claude understands it
Only the words of it tho.
Only the probability of the next token after tokenisation of it.
If 1) you’re smart or practised enough to be able to generate what you’re asking the AI to do for yourself, 2) you’re able to take what the AI generates and debug, check and correct it using non-AI tools like your own brain, 3) you’re sure this whole AI-inclusive process will save time and money, and 4) you’re sure using AI as a crutch won’t cause you brain-rot in the long term, go nuts.
Caveat: Those last two are tricky traps. You can be sure and wrong.
Otherwise, grab the documentation or a bunch of examples and start hacking and crafting. Leave the AI alone. Maybe ask it a question about something that isn’t clear, but on no account trust it. It might have developed the same confusion that you have for precisely the same reasons.
So anyway, Linus clearly fits 1 and 2, and believes 3 and 4 or else he wouldn’t be using an AI. Let’s just hope he hasn’t fallen into the traps.
As I understand it, he doesn’t actually know how to do it himself in python. It also seems like a little side project he’s bullshitting together anyways, so I guess it’s a nice testing ground for trying what it can do. I don’t really see Linus investing a lot of time into learning python.
He’s also made it very clear that he doesn’t want AI slop in the Linux kernel, which is what I’d be more concerned about.
Edit: The project is an attempt to learn about digital audio processing. The visualiser part, not the actual logic, was hacked together from the outset, probably because he’s more interested in the actual processing.
These are – like the analog circuits that started my journey – toy effects that you shouldn’t take seriously. The main design goal has been to learn about digital audio processing basics. Exactly like the guitar pedal was about learning about the hardware side.
From the README of his project, emphasis mine.
I’ve long found it funny how some people claim that generative AI produces terrible slop, and simultaneously that it’s a huge threat to their jobs.
Schrodinger’s
immigrantAi
I wonder how much Google paid him.
Nothing, probably. The whole thing is a fun side project for messing around with audio processing, and he decided to outsource the visualisation part (not even the logic, just the visualisation) because he knows jack shit about python and learning it for just one cosmetic part of the project doesn’t make much sense.
These are – like the analog circuits that started my journey – toy effects that you shouldn’t take seriously. The main design goal has been to learn about digital audio processing basics. Exactly like the guitar pedal was about learning about the hardware side.
Also note that the python visualizer tool has been basically written by vibe-coding. I know more about analog filters – and that’s not saying much – than I do about python. It started out as my typical “google and do the monkey-see-monkey-do” kind of programming, but then I cut out the middle-man – me – and just used Google Antigravity to do the audio sample visualizer.
So this isn’t some paid ad for Google, it’s a busy man pursuing a hobby to learn something and taking a shortcut for a part of the hobby he’s not interested in.
