9 ms·

Show HN: OctoFlow–GPU-native lang, vibe-coded with human at every decision gate

1 points by mr_octopus 7mo ago

mr_octopus 7mo ago
Hi HN, solo developer here. OctoFlow is a GPU-native programming language — the GPU is the primary execution target, not an accelerator you opt into. 4.5 MB binary, zero dependencies, any Vulkan GPU. This is vibe-coded. LLMs generated the bulk of the code. That's not a caveat — it's the point. But "vibe-coded" doesn't mean "unreviewed." Every architectural decision has a human at the gate: pure Vulkan (no CUDA lock-in), zero external dependencies (hand-rolled everything), 23-concept language spec that fits in an LLM prompt, Loom Engine dispatch chains that let the GPU run autonomously. The AI writes code. The human decides what to build, why, and whether it ships. Two principles guide every decision: - Sustainability: Is complexity growing faster than it can be maintained? If the test count drops or the gotcha list grows, stop and fix before shipping more. - Empowerment: Can a non-GPU-programmer go from intent to working GPU code? If a feature makes the language harder for AI to generate, it doesn't ship. What's real today: 966 tests passing, 445 stdlib modules, 150 pre-compiled SPIR-V kernels, interactive REPL with GPU, AI code generation via `octoflow chat`. What's in progress: running 24GB LLM models on 6GB consumer GPUs via layer streaming. The stdlib and everything on GitHub is MIT. The compiler (Rust) is in a private repo for now, but the developer is willing to open-source all of it once there's a team to sustain it. Looking for co-maintainers — especially people with Vulkan experience or who care about keeping languages small and learnable. Happy to answer questions about the architecture, the vibe-coding workflow, or what it's like building a programming language with AI doing 90% of the typing and a human doing 100% of the deciding.
- WalterGR 7mo ago
  But "vibe-coded" doesn't mean "unreviewed." (Just FYI, that’s literally what it means. The term was coined here: https://x.com/karpathy/status/1886192184808149383 https://x.com/karpathy/status/1886192184808149383 . Excerpt: “I ‘Accept All’ always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it.”)
  - mr_octopus 7mo ago
    thanks for that, will change vibe-coded to AI-Assisted then...
    - deleted 7mo ago
      [deleted]

1 points by mr_octopus 7mo ago

Hi HN, solo developer here. OctoFlow is a GPU-native programming language — the GPU is the primary execution target, not an accelerator you opt into. 4.5 MB binary, zero dependencies, any Vulkan GPU. This is vibe-coded. LLMs generated the bulk of the code. That's not a caveat — it's the point. But "vibe-coded" doesn't mean "unreviewed." Every architectural decision has a human at the gate: pure Vulkan (no CUDA lock-in), zero external dependencies (hand-rolled everything), 23-concept language spec that fits in an LLM prompt, Loom Engine dispatch chains that let the GPU run autonomously. The AI writes code. The human decides what to build, why, and whether it ships. Two principles guide every decision: - Sustainability: Is complexity growing faster than it can be maintained? If the test count drops or the gotcha list grows, stop and fix before shipping more. - Empowerment: Can a non-GPU-programmer go from intent to working GPU code? If a feature makes the language harder for AI to generate, it doesn't ship. What's real today: 966 tests passing, 445 stdlib modules, 150 pre-compiled SPIR-V kernels, interactive REPL with GPU, AI code generation via `octoflow chat`. What's in progress: running 24GB LLM models on 6GB consumer GPUs via layer streaming. The stdlib and everything on GitHub is MIT. The compiler (Rust) is in a private repo for now, but the developer is willing to open-source all of it once there's a team to sustain it. Looking for co-maintainers — especially people with Vulkan experience or who care about keeping languages small and learnable. Happy to answer questions about the architecture, the vibe-coding workflow, or what it's like building a programming language with AI doing 90% of the typing and a human doing 100% of the deciding.

WalterGR 7mo ago
But "vibe-coded" doesn't mean "unreviewed." (Just FYI, that’s literally what it means. The term was coined here: https://x.com/karpathy/status/1886192184808149383 https://x.com/karpathy/status/1886192184808149383 . Excerpt: “I ‘Accept All’ always, I don't read the diffs anymore. When I get error messages I just copy paste them in with no comment, usually that fixes it.”)
- mr_octopus 7mo ago
  thanks for that, will change vibe-coded to AI-Assisted then...
  - deleted 7mo ago
    [deleted]