Skip to content

a DepthImage: move the pointer over it

// cat about.md

Hi, I'm Dale. I make tools that make things.

I'm a Rust developer. What I enjoy most is the layer underneath: the grammar, the compiler, the renderer, the framework, so that the thing on top becomes easy to write and hard to get wrong.

That's taken me from proc macros for context-free grammars, to a language for composing music that compiles to MIDI, to Weft, a fullstack web framework with its own template language, Tailwind engine, WebGL renderer and language server. Now I'm laying the foundations for a family of languages of my own with kolang.

I care about sound and light as much as types: fugues, synthesis, shaders, splines and colour spaces turn up in my work as often as GraphQL schemas do. And I care that what I build works for everyone who uses it.

// 01 · how I work

Four things I keep coming back to

Make the language fit the problem

When a problem keeps coming back, it deserves a notation. Music became DSCH; web pages became Weft's templates; grammars became a proc macro.

Accessible by construction

Accessibility belongs in the framework, not a checklist at the end. Every Weft render has an accessibility tree, canvases included, and the tests read it.

Honest numbers

A missing value is not zero, a financial year is not a calendar year, and two units don't share an axis. Charts should say what they don't know.

Tests that use it like a person

Click the button by its name, read what a screen reader would find, fail the build on a CSS class that doesn't exist.

// 02 · the graph

What connects to what

The threads through my work, as a network: thicker lines are stronger ties. Hover or focus a node to see its links.

// 03 · git log --reverse

How I got here

  1. The web, in 3D

    React, Next.js, Three.js and GSAP: landing pages from Figma, a Solana.com rebuild, a React Three Fiber portfolio and ZendoAI, a platform for training image models.

  2. All in on Rust

    Leptos and Dioxus in the browser (ayu, Finoracle), a grammar proc macro (dthc), a multi-threaded composition engine (sound-studies), CLI tools, and ausmetrics, a GraphQL platform for Australian public data.

  3. Services and interpolation

    places-ai, an Axum service that maps the places in a travel site's articles; checking DSCH's interpolation, which ended in Lagrange polynomials; ONNX background removal in rembg-rs.

  4. Music becomes a language

    DSCH spins out of sound-studies as a compiler of its own, with repetition, ramps and a language server.

  5. Weft

    A fullstack framework with its own language and tooling, client sites migrated onto it with weft migrate, weft-cms on top of it, and this portfolio written in it.

  6. kolang

    New tooling for a family of concatenative, functional, scope-delimited languages: DSCH, and in time a general-purpose language for systems programming.