Viewing profile — mr_octopus

Three volumes. Free PDFs. No sign-up. Creative Commons (CC BY-NC-ND 4.0). I kept noticing smart people missing the same things. Not from lack of intelligence — from filters they di…

thanks for that, will change vibe-coded to AI-Assisted then...

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 dependenci…

Three days ago I posted OctoFlow 0.83 here (GPU-native programming language, 2.2 MB binary). The feedback was great. Since then I've pushed v1.0.0 with the thing I've actually been…

Most GPU work boils down to a few patterns — map, reduce, scan. Each one has a known way to assign threads. So instead of writing a kernel with thread_id: let c = gpu_add(a, b) let…

Thanks for trying it! :) Each gpu_* call emits SPIR-V and dispatches via Vulkan compute. Data stays resident in VRAM between calls — no round-trips to CPU unless you need the resul…

The vendor-agnostic GPU approach via KernelAbstractions is great to see. The Vulkan compute path is underrated for this — it runs on AMD, NVIDIA, and Intel without needing ROCm or …

Great writeup. The three-pass softmax is where everyone gets stuck — subtracting the max for numerical stability is one of those things you can't learn from a textbook. The pain po…

I built a general-purpose programming language where the GPU is the primary execution target, not an afterthought. Most languages treat GPU as "write a kernel, dispatch it, copy re…