Why Venutian.

Why a new language

Most languages accrete. They begin as a small idea and gather decades of exceptions, borrowed syntax and compromises made to stay compatible with what came before. The people who write them learn to think around those layers.

We wanted a language nobody has to think around.

Venutian was designed for the moment we are in: people and intelligent machines writing and reading code side by side. Code that reads like a sentence is easier for both to write correctly, easier for both to check, and easier to trust. That is the first principle. Everything else follows from it.

Why English words

Every language carries a theory of the person writing it. Some assume you are a machine and ask you to think like one. Venutian assumes you are a person thinking clearly, and gives you words that already mean what you mean.

A reusable piece of computation is something you make, and what it hands back, you give. A decision is when and otherwise. Truth is yes, and its opposite is no. Every loop is repeat. The shape of your data is a shape. Threads are spawn and await. Even the comment marker, ::, was chosen on purpose.

make greet(name)
    give "Hello, " + name

print greet("world")

Hello, world

None of those words is clever. That is the point. They are the words you would use to explain the program out loud, and they are the ones you type.

Sovereign and first party

Venutian is its own language, not a fork or a reskin of Python, C, Rust, JavaScript or any other. It has its own vocabulary, its own grammar, its own bytecode instruction set and its own virtual machine, designed together and owned end to end.

It is distributed first party. The installer, the packages, the documentation and every update come from one place, venutian.org. There is one Venutian, one vocabulary, one toolchain and one standard of care behind all of it.

The package manager follows the same rule. It writes a content hashed lockfile and verifies every install against it. Nothing arrives on your machine that you did not choose.

Written in itself

A language earns trust when it can build itself. Venutian does.

The full compiler pipeline is written in Venutian: the lexer, the parser, the semantic checker and the code generator, 1,133 lines that emit real, loadable bytecode. Every stage was proven against the original implementation by differential tests, token for token and tree for tree. Beneath it runs a native virtual machine with 69 built in functions.

Venutian compiles Venutian, and every release is built that way.

The name and the mark

The name is a promise about care: proportion, finish and patience. Good tools are checked part by part and nothing is left rough. A language people read aloud deserves the same standard.

The mark is a single monogram in violet and indigo. Everything else on this site is drawn from the language itself: real source, real output and real benchmark rounds.

Closed source, by design

Venutian is proprietary software with a closed source release. The source code is not published, and the language is not open source.

That choice keeps the language coherent. One team decides what the words mean, one toolchain implements them, and one release process ships them. You get a single, coherent Venutian instead of a dozen dialects.

What you build with it is yours. Install Venutian on your own machines and servers, write programs in it, ship them, and build products and businesses on them. The full terms are in the license.

The team

Venutian is designed, built and shipped by a small first party team that writes its own tools in its own language. Project Mirage is our work too.

We describe what Venutian does plainly and show the numbers with their source beneath them. The identifier you read on this site is the identifier you type.

To reach us, see Community.