logoalt Hacker News

timbert • today at 4:00 PM • 8 replies • view on HN

I think we need a new model of software delivery.

Here's my most-recent real-world problem: I wanted to plug in my midi controller keyboard and just play a piano, so I can practice my choral music. Very basic.

This turned into many hours over several days trying multiple DAWs, trying to get tehm to install, get them to run at all, get them to recognize my controller, get them to play a VST plugin...changing system settings, completely jacking up my sound, restoring it all again.

It was a nightmare.

So instead I fired up Claude, worked with it for about 3 hours, and now I have an *8-channel* VST player that supports all my hardware, and includes a snappy UI, with outstanding performance and sound. It's amazing!

I literally spent less time creating a custom solution than I did trying to get the off-the-shelf stuff to work. I could make my player OSS too, but the effort to do that is huge, for all the reasons this forum would understand.

Bespoke software avoids all of that and allows me to do what I want, with the environment I have. I don't have all the features of an FL Studio, but I have what I need, and that works for me, beautifully, at low cost and effort. What's not to like?

So maybe we should share OSS "templates" instead of full products, projects that are the barebones of a solution that you can clone, and have your LLM modify to suit your needs, on your platform of choice.

For example, perhaps my barebones VST player is mostly good enough for you, but you also want to play sound fonts? Cool, clone my project, instruct your LLM to add sound font support, and add support for your controller or your output device. Or convert it from Gnome to KDE.

The time and cost of doing this is so little now, why not? I'm getting more out of my computer than ever, and I'm happy about that :)


Replies

nayroclade • today at 4:16 PM

Yes, right now this is absolutely the best way to build bespoke software, but it is also very wasteful. Think of all the time and the billions of tokens being burned to repeatedly reimplement apps and features. LLMS code fast, but not yet instantaneously or perfectly for complex features.

What we need is more than just OSS templates. We need fully LLM-managed "software libraries". These would be like package managers on steroids. They would be a huge hierarchy of LLM-coded modules. When you ask for an app, your LLM assembles it from the modules that already exist. If you ask for a novel feature, it codes it up and places it into the library.

So, for your VST player example. You would ask for a barebones version with just the features you need, and your LLM would assemble it for you from preexisting library modules. Then you ask for sound font support. If there is an existing sound font module, it would download it and add it into your app. If there wasn't, it would create one and put it into the library, so the next time someone asks, they can quickly get a VST player with sound font support.

➕ show 2 replies
pitchlatte • today at 6:21 PM

as someone who’s been working with MIDI for a hot minute, I’m really puzzled by your experience. either you have a very fussy controller or you received bad advice. most samplers like Kontakt and modellers like OrganTeq (very well regarded organ modeller) literally comes with a standalone version so that you don’t need to fire up a VST engine/DAW.

montenegrohugo • today at 4:12 PM

Fully aligned, i echo the above experience strongly.

However, it seems to me like there must be some middle ground, between sharing architecture "ideas" and full on code PRs.

I myself maintain various FOSS projects; and incoming PRs are marginally useful. generally i just close, and copy with claude following my own & project taste (crediting initial contributor).

rabf • today at 5:42 PM

I think supplying the solid base on which to build along with instructions for a users LLM is very valuable just now.

ValdikSS • today at 4:29 PM

>So maybe we should share OSS "templates" instead of full products, projects that are the barebones of a solution that you can clone, and have your LLM modify to suit your needs, on your platform of choice.

I've seen this idea: https://v-it.org/

➕ show 1 reply
larodi • today at 4:07 PM

readers here who have never tried this or does not understand what the person is talking bout - dare not speak. really, you have no idea, so please scroll further. those who understand will surely upvote. because _this_ is what savvy and pragmatic people (would and does) do in 2026 in order to get stuff done, perhaps they did otherwise back in 2012, but not anymore.

➕ show 1 reply
augment_me • today at 4:12 PM

This is a take that is outdated if not now, then in 3 months.

These has been this ladder of copium that "oh human still has input here for X, oh shoot it doesn't with Claude 4.5, well human is still needed for Y, oh shoot...".

You are suggesting that you can provide context that the model can't on its own. This is a search problem, every iteration it gets better.

We are at the stage in our company where "/goal optimize this" gets better result than any biased human context engineering can provide.

➕ show 2 replies
rewgs • today at 6:39 PM

> I wanted to plug in my midi controller keyboard and just play a piano, so I can practice my choral music. Very basic. > > This turned into many hours over several days trying multiple DAWs, trying to get tehm to install, get them to run at all, get them to recognize my controller, get them to play a VST plugin...changing system settings, completely jacking up my sound, restoring it all again.

Hate to say it but this is genuinely just a skill issue.

Resorting to building a DAW tailored to your own lack of understanding because you can't be bothered to learn tools that are extremely widely used and well-documented is the most extreme case of yak-shaving I've ever seen.