Hacker News new | past | comments | ask | show | jobs | submit
They may seem like small details, but I think a couple novel design decisions are going to prove to be widely adopted and revolutionary.

The biggest one (as Karpathy notes) is having skills for how to write a (slack, discord, etc) integration, instead of shipping an implementation for each.

Call it “Claude native development” if you will, but “fork and customize” instead of batteries-included platforms/frameworks is going to be a big shift when it percolates through the ecosystem.

A bunch of things you need to figure out, eg how do you ship a spec for how to test and validate the thing, make it secure, etc.

How long before OSs start evolving in this way? You can imagine Auto research-like sharing and promotion upstream of good fixes/approaches, but a more heterogenous ecosystem could be more resistant to attacks if each instance had a strong immune system.

> having skills for how to write a (slack, discord, etc) integration, instead of shipping an implementation for each

I'm not sure what is the advantage. Each user will have to waste time and tokens for the same task, instead of doing it once and and shipping to everyone.

loading story #47366907
loading story #47367249
I get the appeal but I disagree

The strength of open source software is collaboration. That many people have tried it, read it, submitted fixes and had those fixes reviewed and accepted.

We've all seen LLMs spit out garbage bugs on the first few tries. I've written garbage bugs on my first try too. We all benefit from the review process.

I would rather have a battle tested base to start customizing from than having to stumble through the pitfalls of a buggy or insecure AI implementation.

loading story #47366003
loading story #47367158
I have thought of this ship a spec concept. What is we are just trading markdown files instead of code files to implement some feature into our system?