· 5 min read
Five languages with no committee
A tour of five creator-led languages from Reddit shows that tiny languages are strongest when they pursue one rude idea and weakest when they try to become an ecosystem.
I searched creator posts in r/ProgrammingLanguages and threw out anything with a company, foundation, or obvious user base. I wanted languages you could still mentally fit inside one person's head.
These five repositories had between four and 212 GitHub stars when I checked on July 12, 2026. Stars are not quality scores. Here they are just proof that we are safely inside the garage.
R3
★ 212the whole computer is a stack
Lax
★ 54grammar belongs to the programmer
TensaLang
★ 76attention should be source code
multilingual
★ 10one AST, many human languages
Dragonstone
★ 4Ruby, but every switch is optional
no foundation · no steering council · package manager possibly imaginary
First, the five dialects of “I can fix programming”:
:main 0 sdlcls $ff0000 sdlcolor 10 10 100 100 sdlfrect sdlredraw ;function { {year} is a leap year } { if year % 400 == 0, return true if year % 100 == 0, return false return year % 4 == 0}fn attn_scores(q: Tensor<f32, [H, D]>, k: Tensor<f16, [T, D]>) -> Tensor<f32, [H, T]> with tile=[8, 64], parallel=[h, t] { scores[h, t] = sum(i) q[h, i] * (k[t, i] as f32) return scores}soit somme = 0pour i dans intervalle(4): somme = somme + iafficher(somme)con limit: int = 10var x = 1024while x > 0 echo x x //= 2endR3: the complete tiny computer#
phreda4 presented R3 as a ColorForth-inspired language for recreational programming. The repository contains the language, a roughly 40 KB C VM, a self-hosted compiler, an editor, and SDL-backed graphics and game tools. That coherence is the win: clone one strange little world and start drawing.
What works
It has a point of view all the way down. The language, VM, tools, and demos agree about what R3 is for.
What bites
The data stack is invisible, the vocabulary is alien, and the core mostly treats values as 64-bit words. Team readability is not the project.
VerdictBest tiny system. I would keep it installed for fun, not payroll.
Lax: grammar as user space#
Lax's creator wanted functions to define their own sentence-shaped call patterns. The compiler and VM combine those patterns with static typing, inference, bytecode, and an experimental JIT. This is not prettier parentheses. It is mixfix syntax treated as the normal function interface.
What works
It is the most interesting language-design idea here. A domain API can read like its domain without waiting for a macro system to bless it.
What bites
Every module can become a dialect. Ambiguity, formatting, search, documentation, and onboarding all inherit the grammar. One Reddit commenter called it “99 languages in a trench coat.”
VerdictBest research toy. Worst language to discover during an incident.
TensaLang: the one with a job#
Ben Chaliah introduced TensaLang as a tensor-first language where an inference forward pass, reductions, tiling, and parallel dimensions live in source. The compiler lowers through MLIR to an LLVM JIT on CPU or NVVM on CUDA.
What works
It attacks a real seam: model code and scheduling decisions are visible instead of buried across a runtime and a pile of kernels.
What bites
The scheduling hints leak hardware into source, the toolchain is heavy, and the current backend story is mostly CPU plus CUDA. This is a research compiler, not an ecosystem.
VerdictMost convincing language here because it refuses to be general purpose.
multilingual: semantics before spelling#
John Samuel's multilingual keeps one semantic core beneath English, French, Spanish, and other surfaces. The current implementation has a browser playground, cross-language module imports, Python execution, and WAT/Wasm output. The experiment is better than simple keyword substitution because the shared AST is the actual product.
What works
It separates program meaning from the historical accident that most syntax keywords are English. That is useful for teaching and tooling research.
What bites
Natural languages do not share word order, reserved words collide, and translated syntax can still feel foreign. The roadmap also sprawls into AI, multimodal, reactive, and distributed programming.
VerdictKeep the semantic-core experiment. Ruthlessly cut the platform pitch.
Dragonstone: ambition without a knife#
Vallereya's Dragonstone is a Ruby-and-Crystal-inspired language with an interpreter, compiler, optional explicit types, classes, mixins, enums, LLVM and bytecode targets, and a self-hosting effort. The creator is refreshingly open about the unfinished repository: garbage collection, a borrow checker, FFI, concurrency, package management, and editor tooling are all still moving.
What works
There is real implementation behind the feature list, and the syntax has the easy familiarity of a Ruby-family language.
What bites
Optional typing, optional GC, an optional borrow checker, multiple backends, OOP, FFI, and self-hosting multiply each other. One contributor cannot test every combination into coherence.
VerdictCut 70 percent. The remaining 30 percent might become a language people can describe.
A tiny language does not need a market. It needs an opinion worth stealing.
R3 says the environment matters. Lax says grammar is an API. TensaLang says scheduling belongs beside the tensor program. multilingual says semantics should survive translation. Dragonstone accidentally supplies the control case: saying yes to everything is not a thesis.
I would not build a company on any of these tomorrow. I would steal something from four of them today. That is the point of small languages. They can afford to be wrong in one interesting direction before a committee rounds the idea back into Java.