Say what can change.
let for an immutable binding. mut when a value should change. Types are inferred, or written explicitly.
let name = "CHUD";
mut count: int = 0;
count += 1; INTRODUCING CHUD 0.1.0-alpha A language
A language
of its own.
Native to the core.
Your code. A native executable. A workspace built around both. Meet CHUD, an independent programming language and its dedicated IDE.
Windows x64 first. A working alpha, built from source.
WRITE CHUD. BUILD NATIVE..chud
C Program.chud
chud CHUD.App;
use CHUD.Core;
public func Main() -> int
{
CHUD.Print("Hello from CHUD!");
return 0;
}›_ Expected outputWindows x64
Hello from CHUD!
C Bindings.chud
let language = "CHUD";
mut count: int = 0;
const LIMIT = 3;
while count < LIMIT
{
CHUD.Print(language);
count += 1;
}›_ Expected outputWindows x64
CHUD CHUD CHUD
C Functions.chud
func Square(value: int) -> int
{
return value * value;
}
mut total = 0;
for number in 0..10
{
total += Square(number);
}
CHUD.Print(total);›_ Expected outputWindows x64
285
Ahead-of-time compilationRead the walkthrough
.chud Source filesNative Machine-code outputStatic Type checkingCHUD Studio Your workspace
01 / THE LANGUAGEFamiliar shape.
Familiar shape.
Independent thinking.
Clear bindings, explicit function signatures, and useful compiler diagnostics. Small enough to learn. Real enough to run.
Explore the language referenceFunctions, without the ceremony.
Typed parameters. A clear return type. Scoped locals and compile-time checks that catch mismatches.
func Add(a: int, b: int) -> int
{
return a + b;
}Built to leave the editor.
The frontend produces LLVM IR, then native objects and an executable. Your compiled app runs independently of Studio.
Follow the compilation pipeline02 / CHUD STUDIOYour language.
Your language.
Your workspace.
A dedicated desktop IDE, from the first line to the final build. An actual editor connected to your actual CHUD project.
Meet your new workspace CHUD STUDIO · ACTUAL APPLICATION
Make room for your code.
Syntax highlighting, multiple tabs, split editing, find and replace, and autosave settings.
Build it. Run it. See it.
Compiler diagnostics, real build output, exit codes, and PowerShell command execution.
A second pair of eyes.
Ask ChudGPT with context you choose. Inspect a diff before applying proposed code changes.
And yes, it works with Discord.
Set it up Optional Rich Presence. One toggle. Share your project and filename only if you choose.
03 / LEARN CHUDLess guessing.
Less guessing.
More building.
Documentation for the language that exists today. Start with a native Hello World, then go a little deeper.
GET STARTED 01From zero
Read it.
A folder.
From zero
to CHUD.
Set up the Windows toolchain and open your first workspace.
Installation guide →LANGUAGE GUIDE 02Read it.
Write it. Run it.
Bindings, types, functions, control flow, and the rules behind them.
Language reference →PROJECT TOOLS 03A folder.
A native app.
Understand chud.toml and the commands that make a project work.
Projects & CLI →AN ALPHA, OPENLY.
A working beginning.
A deliberate way forward.
The compiler, core language, project tools, and Studio are here. Advanced types, packages, debugging, and a public installer are still ahead. Follow what works and what’s next.
See the status & roadmap