Skip to main content

Posts

Showing posts with the label Programming

Tessel: A Tiny Declarative Language for Building Native Desktop Apps

Most tools for building a desktop app ask you to make a lot of decisions before you've written a single line that does anything: pick a framework, wire up a build system, set up a project structure, manage dependencies, configure a packager. Tessel throws all of that out. It's a small declarative programming language where a folder of .tsl files is the program — and the whole thing compiles down to a tiny native app for macOS and Windows. Here's a tour of what makes it interesting. A whole app in one block The clearest way to understand Tessel is to look at a complete program. This is a working counter app — not a snippet, the entire thing: You declare an app with a window size, a piece of state , and a tree of views — VStack , HStack , Text , Button — described the way they should look. Run it with tessel run counter.tsl and a real window opens. There are no project files, no imports, and no build configuration to write. If you've ever bounced off deskt...

The History and Legacy of Java: Write Once, Run Everywhere — for 30 Years

Few technologies have shaped the modern world as quietly and completely as Java. It runs on the servers behind your bank, the Android phone in your pocket, the world's most popular video game, and the data pipelines that train today's AI. Three decades after its debut, Java is still one of the most-used programming languages on Earth. This is the story of how a language built for interactive TV ended up running the planet. From a set-top box to the browser (1991–1995) Java began in 1991 as an internal Sun Microsystems skunkworks effort called the Green Project , led by James Gosling , Mike Sheridan, and Patrick Naughton. Their goal wasn't the web at all — it was consumer electronics, like smart TVs and set-top boxes. Gosling designed a small, portable language originally named Oak (after a tree outside his office). The interactive-TV market never materialized, but the team had built something more valuable than they realized: a language whose programs could run on an...

Edsger Dijkstra: The Man Who Made Code Elegant

Every time your phone finds the fastest route home, a piece of a Dutch physicist’s 1956 idea is running under the hood. Edsger Wybe Dijkstra (1930–2002) is one of the true founders of computer science — the rare figure who gave us both an algorithm you use every day and a way of thinking about programming that still shapes the field. This is his story. The accidental programmer Born in Rotterdam in 1930, Dijkstra trained as a theoretical physicist at Leiden. But in the early 1950s he discovered a brand-new profession that barely existed yet — programming — and was so taken with it that he made it his career, becoming, by some accounts, the first professional programmer in the Netherlands . When he married, the registrar reportedly wouldn’t accept “programmer” as an occupation, because it wasn’t recognized as a real job. He wrote down “theoretical physicist” instead. The 20-minute algorithm In 1956, while sitting...

C++26 Is Here: The New Features That Actually Matter

Every three years C++ gets a new standard, and they’re not all created equal. C++23 was a tidy, incremental update. C++26 — finalized by the ISO committee in March 2026 — is the big one : the most significant leap the language has taken in a decade. It lands three landmark features at once, makes the language meaningfully safer by default, and sprinkles in dozens of quality-of-life upgrades. Here’s what actually matters. 1. Compile-time reflection (the headliner) This is the feature C++ programmers have wanted for 20 years. Reflection lets your code inspect itself — types, members, enums — and generate new code, all at compile time . It introduces a new operator, ^^ (yes, informally the “cat-ears operator”), to reflect an entity, and a splice syntax [: :] to turn a reflection back into code. constexpr auto r = ^^int; // a reflection of the type "int" using T = [: r :]; // splice it back into real code → T is int ...

HTTP Just Got a New Method: Meet QUERY (RFC 10008)

For 25 years, web developers have gotten by with a familiar handful of HTTP methods: GET, POST, PUT, DELETE, PATCH. In June 2026, the list officially grew. Meet QUERY — standardized as RFC 10008 by the IETF, with authors from Cloudflare, Akamai, and greenbytes. It’s the first genuinely new, general-purpose HTTP method in a very long time, and it fixes a problem developers have hacked around for years. The problem QUERY solves Say you’re building a search or filter endpoint. You have two bad options: Use GET and cram everything into the URL query string. This is “correct” (search is safe and repeatable), but URLs have length limits, complex/structured queries are painful to encode, and your search terms end up in server logs, browser history, and proxy caches. Use POST and put the query in the request body. Now you have room for a rich query — but you’ve lied about your intent. POST is neither safe (it’s allowed to change ...

Python Without the Interpreter: What '3.14 Compiled to Metal' Means

Python is beloved for being easy and hated for being slow. A recurring dream in the community — compiling Python straight to native machine code, with no interpreter in the loop — keeps inching closer. Here’s what that actually means. The “interpreter tax” Normally, Python code is turned into bytecode that a virtual machine executes line by line at runtime. That indirection is why Python is flexible — and why it’s slower than languages compiled ahead of time to raw CPU instructions. Every operation carries overhead the CPU wouldn’t otherwise pay. What “compiled to metal” means The idea is to translate Python — or a well-behaved subset of it — directly into native machine code, so the CPU runs your logic without the interpreter middleman. Done well, hot numerical and loop-heavy code can approach the speed of lower-level languages. The trade-offs There’s no free lunch. Python’s most dynamic features...