13 articles in this category
Every error message is a tiny autobiography. It tells you, in a few terse lines, what the language's designers cared about most: where they drew lines...
After a decade of building programming languages—some for fun, others for production—I've learned one brutal lesson: the hotter the forge, the easier ...
There's a steel hinge on my garden gate. After three winters of rain, it started sticking. Not enough to slam, but enough to make you push harder. The...
A language that reads like poetry can run like a snail. A language that screams at clock speed can read like hieroglyphics. The tension between readab...
So you're building a language. Or maybe you're maintaining one. And there it's — the same wall everyone hits: speed wants raw memory access, unsafe ca...
When you pick up a language, you want tools. But what if the toolbox is so stuffed that you spend more time choosing a hammer than driving nails? That...
Imagine a balancing scale. On one side, you place readability—the ease with which a human can understand, debug, and modify code. On the other side, y...
You open your code forge, stoke the fires, and... nothing. The program crawls. Memory spikes. Fans spin like a jet engine. If you've been there, you k...
Imagine a gear with a broken tooth. The machine keeps running, but each rotation grinds metal. Eventually, the whole system seizes up. That is what ba...
Language design is like forging a tool. You want enough handles to let users grip the language firmly in any situation. But add too many, and the tool...
So you are choosing a programming language for a new project—or maybe you are a group lead whose developers keep reinventing wheels when they should b...
You're two months into a project. The codebase has grown from a tidy script to a sprawling beast. New hires are stepping on each other's toes. That on...
Here is the problem: you want your language to run fast, really fast, but you also need it to not crash, leak memory, or let attackers in. Every desig...