Native is one of those words that means different things depending on context and your background. For me, native means actual binary code running on the machine, not through a JVM or V8 or anything of the sort.
In the Apple world, Native usually means using the system UI components and the Apple guidelines.
Not the best title. It is not "for C", but in C. And currently useable on desktop + web but after looking at the project I think it will quickly be ported on mobile etc.
There are some libraries that use native widgets on each platform, e.g. libui-ng. Although the issue with things like this is that you aren't going to be able to use all of AppKit, and you get forced into the lowest common denominator expressable by all platforms.
A good middle ground might be having platform-specific pieces but expressed using a more standard domain-specific language. E.g. technically you can already wire up GUIs without interface builder but it's quite verbose. There should be some simpler way to express layout constraints and have button callbacks.
What purpose would that serve? You have the source code. In the old days we’d just share tarballs. No provenance. It’s fine. You have the unit of legible modifiability.
There have definitely been times when I've cloned repos that were vibed, pointed my own agent at it, and then hacked up whatever changes I've wanted. I don't think there's been a single time that a lack of prompts has caused any issues, but there have been at least a few times where stuff like AGENTS.md checked into the repo has caused hiccups from them encoding stuff that conflicts with how I want things done.
Exactly. Some "Prolog interpreter in Tcl" is a prompt away in LLMs but what's the point of inferring and dumping it on github? Same goes for any vibe-coded project.
reply