the wall was never real
A programming language that reads like plain sentences.
Vision is a small, legible systems language. No symbols to decode — it spells things out in words, compiles to C, and stays readable all the way down.
to fingerprint, given the contents: begin a blake3 hash giving the hasher feed the contents to the hasher finish the hasher giving the result answer the result
Real Vision. It compiles and runs.
readable by design
Code you read like a sentence.
Other languages make you decode symbols. Vision spells the same logic out in words — so the line tells you what it does.
if (x == 5) { … } if x is 5 total += step; the total is the total plus the step for (int i=0;i<n;i++) for each item in the items return total; answer total try { … } catch (e) { … } but if it can't be done, … and stop effects made visible
You can see what a line does.
Vision marks the lines that reach outside your program or can't be undone — by law, checked by the compiler. An unmarked line is provably calm.
>>touches the world (disk, network, clock)!!can't be undone — e.g.>> !!remove the file
Side effects can't hide. The dangerous line can't read as gently as the safe one. No mainstream language does this in such plain form.
to save the note, given the words and the path: the temp path is "{the path}.tmp" >> write the words to the file at the temp path >> make sure the file at the temp path is saved >> rename the file at the temp path to the path
this program understands blake3 to hash some bytes is blake3_hash it takes some bytes it gives back some bytes to fingerprint, given the contents: the hash is hash the contents answer the hash
No pointers, no lengths. The compiler handles the mechanics.
forty years of libraries
Forty years of C libraries, in plain Vision.
You describe what a C function does — what it takes, what it gives back — in Vision. The compiler handles the rest. You never write a pointer.
Crypto, audio, compression, databases — reached without leaving Vision.
explicit by law
The compiler won't let you ignore failure.
If something can fail, you handle it with but if.
There is no silent error, no forgotten check — the language refuses
to compile until every failure has an answer.
read the file at the path giving the contents but if it isn't there, say "nothing to read there" and stop but if it can't be read, explain why and hand it on
no silent corruption
No hidden precedence. No silent corruption.
a plus b times c won't compile — Vision
asks you to group it, so the order is always on the page, never a rule
you have to remember.
a plus b times c // won't compile — group it
a plus (b times c) // the order is on the page
A wrong order silently corrupting a value is the kind of bug Vision refuses to allow.
the honest facts
What it is.
- A small systems programming language. Compiles to C.
- Reads like sentences: words, not symbols. Indentation makes blocks.
- Memory is automatic. Failure is explicit. Effects are visible.
- Owned and verifiable: zero telemetry, no hidden anything.
- Built by one person, in the open. Hope in every line.
next
Start reading.
The docs are calm, plain-spoken, and quick — the shape of the language without the fog.
Source at kepr.uk/vision