Thirteen posts ago this series started with a bit-crusher written in Object Pascal. Time to close the loop with a look at the stack I actually work in today — Go on the backend, TypeScript and React on the frontend — and at the place where all current work is visible at once.
Why Go
Go won me over for the same reasons Pascal did in the nineties: it is explicit, it compiles fast, it produces a single binary, and it refuses to be clever at the reader’s expense. For DSP work it adds something Pascal never had out of the box — effortless concurrency and a testing/benchmarking culture built into the toolchain. The algo-* suite, go-dws, the graphics ports, gll-tools and the PipeWire experiments from the previous posts are all Go, and none of them would have been more fun in any other language I know.
Why TypeScript
Where things need a face, I reach for TypeScript and React. That, too, has a longer history than it looks: my first typed-web experiments ran through ts2pas and DWScript’s JavaScript backend a decade ago, and today projects like the algo-drum machine or the block-based DWScript editor (dwscript-blocks) are straight TypeScript. I also work daily with AI-assisted development workflows and enjoy exploring what they make possible.
A living portfolio
This site preserves the history; the present tense lives at cwbudde.github.io — a small React app that reads my public repositories live from the GitHub API. Nothing there is curated by hand, so it is always current by construction: whatever I pushed last week is already on it. If this retrospective series made you curious what happens next, that page — and github.com/CWBudde directly — is where to look.
Thanks for reading along. The archive pages on this site will stay where they are; the blog is where new things will appear from now on.