Go on NoRaincheck

Beating FastAPI

Wed, 15 Jul 2026 00:00:00 +0000

One thing which Go does a lot better than Python is single binary deployments. As an experiment I thought, why not have a way to package up Go as part of a Python package, similar to maturin - and also have a way to spin up a Python webserver that is packaged as a Go binary.

The results were definitely interesting:

Go binary had 9x more throughput than stdlib Python’s http library, and ~5x more throughput than FastAPI
Idle memroy usage was `3x higher for FastAPI, and the peak memory usage was ~2x higher than Go binary

Of course the pocket python restriction may be too much for more complex applications.

Testing Go with Monty (Python)

Wed, 01 Apr 2026 00:00:00 +0000

Testing Go with Monty (Python)

April 2026

Not much to say right now besides it works.

 1package main
 2
 3import (
 4	"context"
 5	"fmt"
 6	"log"
 7
 8	monty "github.com/ewhauser/gomonty"
 9)
10
11var a = `
12def add(x):
13 return x + 1
14
15add(x)
16`
17
18func main() {
19	runner, err := monty.New(a, monty.CompileOptions{
20		Inputs: []string{"x"},
21	})
22	if err != nil {
23		log.Fatal(err)
24	}
25
26	value, err := runner.Run(context.Background(), monty.RunOptions{Inputs: map[string]monty.Value{"x": monty.Int(10000)}})
27	if err != nil {
28		log.Fatal(err)
29	}
30
31	fmt.Println(value.Raw())
32}

It will be interesting if this enables greater scripting capabilities when integrating things into other languages.

Maya1 vs Kokoro vs Kitten TTS Review

Sun, 01 Mar 2026 00:00:00 +0000

Maya1 vs Kokoro vs Kitten TTS Review

March 2026

I finally got to test TTS models, and got them running locally with a variety of notes.

Kitten: advertised as the smallest model, its also the easiest to setup
Kokoro: an extremely good model for its size. I found getting it setup with the onnx wrapping to be the most straightforward (supports quants!)
Maya1: supports gguf. I ended up hosting it in LM Studio with a wrapper to have it working. This is the best quality but also the slowest

TLDR: Use Kokoro if you want a good balance of speed and quality, otherwise Maya1 is a suitable model if you’re willing to wait a bit

In Appreciation of Go Generate

Mon, 01 Sep 2025 00:00:00 +0000

In Appreciation of Go Generate

September 2025

Go is a rather minimal language. It does away with macros and (direct) metaprogramming, but it does offer code generation as a first-class citizen via go:generate . On multiple counts, it is rather unassuming and underwhelming, after all the code generation needs to be directly committed for it to be used; there’s no generators or run time generation, but rather it forms part of the distribution.

Inlay Hints and LSPs

Sun, 01 Jun 2025 00:00:00 +0000

Inlay Hints and LSPs

June 2025

It’s currently 2025, and there is a massive amount of interest in LLM/AI powered IDEs. But I think there is something more powerful - making good use of your LSPs. In particular inlay hints. Now inlay hints are a somewhat recent addition, but its something that helps with inferring type hints or annotating your code with these hints to reduce mental strain.

Python: pyrefly adds support by default
Rust: rust-analyzer adds support by default
Go: gopls adds support – you may need to enable it in settings

In VSCode settings it would look like:

rqlite - a Production Experiment

Wed, 01 Jan 2025 00:00:00 +0000

rqlite - a Production Experiment

January 2025

rqlite is a distributed version of sqlite using the raft consensus algorithm. The great thing about rqlite actually has nothing to do with the underlying tech, but more to do with broad developer experience and that is the defaults with the provided helm charts.

It just feels like I’m the target audience - someone who wants to quickly push rqlite to production with the minimal dependencies and gives me enough to shoot myself in the foot. Compared with postgres helm charts, rqlite presumes that you may want to just use it as-is, without even a values file. That is a welcome change, whereas almost anything from the bitnami one expects you as a developer will make modifications. Something in that model does not feel quite right. This friction (although seemingly trivial) converted me to use rqlite (the other reason is I was using sqlite for my tests which meant I didn’t need to worry about changing any code to ensure compatibility between different sql dialects).