upvote
Yes, plus there is the fact that there is a HUGE amount of open source audio code out there, many, many DAW’s and so on.

I chalk it up to synth and audio guys being among the more innovative users, personally - its a market of folks who have always wanted to design their own DSP/audio-graphs, and were primed for the opportunity that AI/ML presented to do so.

The same goes for the vibe-coded game communities, and as well all the retro guys.

Folks tend to not realize just how much open source is out there in fields/subjects they’re not really familiar with.

reply
Also the 1 Million token context window helped make it more viable.

I've made a bunch of unreleased vibe-coded VST plugins to replace the hundreds that I've bought over the years - and many of the barriers to development weren't the model. Just having belief that the model was capable of the work, a bit like the 4-minute mile. Also knowing to persevere and iterate with the model, not giving up because the first UI is inevitably so amateurish.

There's also a flywheel happening. If you make permanent notes on the process, your rules for UI design, a library of re-usable components and algorithms, tools so the model can judge its own work... the whole process for the next VST just gets much faster & much easier. Same goes for any software you make with AI too.

reply
so weird how AI boosters act like it hasn't been less than a year, isn't it?
reply
It hasn't been. Since Opus 4.5 "letting Dario take the wheel" became useful for the vast majority of programmers.

As of this fall, you are being professionally irresponsible and SHOULD NOT be working in the field if AI is not integral to your SDLC. At a minimum it should be checking your code for bugs and vulnerabilities.

reply
There are legal issues, ethical issues, moral issues, aesthetic issues, economic issues, financial issues, availability issues, longevity issues, consistency issues, reproducibility issues, sovereignty issues, regulatory issues, licensing issues, terms of service issues, and data retention issues that need to be addressed before AI can even be permitted in my software development life cycle - much less made mandatory on pain of unemployment.
reply
What about security issues? What about the fact that if AI isn't hardening your code under your control, it's hacking it under an adversary's?
reply
Did it come across as dismissive of security issues? I apologise. The security issues are exactly what’s being weighed against those other issues. Both the security issues and the other issues are valid issues and it’s valid to weigh them against each other.

And I sort of understand what you’re trying to say in that second line, something along the lines of “the only thing that stops a bad guy with a gun, is a good guy with a gun”, right? Unfortunately it’s poorly phrased.

If AI isn’t hardening my code, then my code is very vulnerable to AI hacking from an adversary, I’ll grant that. But an absence of my AI does not cause the presence of an adversary’s AI in the way that the binary construction claims. (Compare “if you’re not with us, you’re against us”, which is a threat that says the absence of your fealty does cause the presence of my hostility.)

Likewise, I’ll grant that AI hardening my code does mitigate the damage from AI hacking, but again its presence does not cause the absence of an adversary’s AI hacking in the way your phrasing says it does.

reply
this is what i'm talking about
reply