Venk: a Rust-built language with a built-in raylib 3D engine reaches first beta

A language that ships with its own engine

A solo developer has announced the first public release of Venk, a programming language implemented in Rust and aimed squarely at 2D and 3D game development. According to the announcement on dev.to, Venk is a fully independent language with its own lexer, parser and interpreter, and its central idea is that a game language should arrive with its engine already attached — what the author describes as batteries included, drawing a contrast with Python and GDScript.

The project grew out of a familiar frustration, the post explains: starting a game project in Rust means wrestling with OpenGL and a pile of dependencies, sometimes for hours, before anything appears on screen. Venk is an attempt to eliminate that setup cost by moving the rendering and maths plumbing inside the language itself.

What ships in version 0.0.1

The built-in 2D/3D engine is powered by raylib, and the announcement lists native support for 3D cameras, vectors, sprites, particle systems and collision detection from day one. Procedural generation is treated as a core feature too: built-in noise functions are intended to let developers produce large, RimWorld- or WorldBox-style worlds in a handful of lines of code.

On performance, the developer claims that because the interpreter is written in Rust and the heavy numerical work is handed off to the Rust backend, the language can render 10,000 particles at a stable 60 FPS. That figure comes from the project's own post rather than independent testing, so it is best read as a claim for now.

The syntax is described as a blend of Rust and Python, prioritising readability. The example program in the announcement shows the shape of it: a main function opens a window, creates a 3D camera through a vek3d_camera_create call, then runs a loop that clears the screen, draws a grid and a red cube, and exits once the window is closed — a dozen or so lines for a minimal but complete 3D scene.

Trying it out

Venk is open source, and the beta is currently Windows-only. According to the release notes linked from the post, getting started means downloading venk.exe and raylib.dll from GitHub, placing both files in the same folder and running the executable — either to drop into an interactive console or to run a script such as game.venk directly. The author notes that a graphical IDE and a standalone executable bundler are not part of this release and are still in development.

What is planned next

The roadmap in the announcement names three items: a graphical IDE with a built-in code editor, a bundler that packages a finished game into a single shareable executable, and — most consequentially — an LLVM backend that the developer says should lift performance to the level of natively compiled C++. The author also acknowledges that this is the very first beta and that bug fixing is ongoing, inviting feedback on the syntax and the engine.

Why it matters

Setup friction is one of the most commonly cited reasons newcomers bounce off game development, and it is the same reasoning that pushed engines like Godot toward tightly coupled, purpose-built scripting languages. Venk takes that idea to its logical endpoint: not a library you install, and not an engine with a scripting layer bolted on, but a language whose standard library effectively is the engine.

The caveats are significant. This is a v0.0.1 beta from a single maintainer, it runs only on Windows, and as an interpreted language its long-term performance prospects hinge on the promised LLVM backend actually materialising. It is therefore an experiment to watch rather than a production tool today. Even so, it is a useful data point in two ongoing trends: the search for lower-friction on-ramps into game development, and Rust's growing popularity as a substrate for building other languages and tooling.