Letting an LLM write executables byte by byte (hello world to playable Tetris)
NLC: an LLM that writes executables directly No source language. Give an LLM a natural-language spec and it returns the bytes of the executable: ELF header, program header and machine code, by hand. The only thing between the model and the binary is xxd -r.
- ▪NLC: an LLM that writes executables directly No source language.
- ▪Give an LLM a natural-language spec and it returns the bytes of the executable: ELF header, program header and machine code, by hand.
- ▪The only thing between the model and the binary is xxd -r.
Hacker News (AI / LLM) files mainly under ai. We currently carry 7,541 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | GitHub |
| Canonical URL | https://github.com/lusob/nlc |
| Publication time | Sun, 04 Oct 2026 14:48:16 +0000 |
| Retrieval time | 2026-10-04T14:59:55.455Z |
| Last seen | 2026-10-04T14:59:55.455Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | cVI9kQ2IZvhk · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
NLC: an LLM that writes executables directly No source language. No compiler. No assembler. No linker. Give an LLM a natural-language spec and it returns the bytes of the executable: ELF header, program header and machine code, by hand. The only thing between the model and the binary is xxd -r. A 439-byte HTTP server, generated from a one-paragraph spec. That's the real output of the generated binary. I've been running this experiment every time a new model comes out for a couple of years, and this is the first time the results are good enough to share. You could say it isn't a compiler in the classical sense, but a model acting as the entire compiler (analysis, code generation, assembling and linking) in a single step, inside a loop that corrects it.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at GitHub.