Tags / Go

Go

Projects

Trading infrastructure Active 2025

Go Backtester

A custom backtesting engine built for strategies that stopped fitting neatly inside off-the-shelf Python frameworks.

Go Trading Backtests Data Analysis

Read the story 2 connected posts

Go UI framework Active 2026

godom

A Go framework for local apps where the Go process owns the DOM and the browser is just a screen. No Electron, no complex JS frontend, no API layer; go build gives you one binary that opens a tab.

Go JavaScript AI Claude Code

Read the story 13 connected posts GitHub

Orbital diagram representing planetary ephemeris computation

Go library Active 2026

goeph

A Go ephemeris toolkit built on NASA JPL ephemeris data, born from porting a real Skyfield-based workflow. Now the bedrock for further tooling in this space.

Go Astronomy

Read the story GitHub

Posts

A three-stage diagram of the tutorial app. Stage 1: a single counter card. Stage 2: counter and todos cards side by side on one page. Stage 3: a top nav (Dashboard, Counter, Todos) with the dashboard view showing the counter and a summary card, plus arrows indicating shared state between Counter and Summary, and between Todos and Summary.

How to use godom

May 11, 2026

Building a small godom app in three stages: a counter, two islands on one page, then a multi-page layout with a shared-state dashboard.

A diagram of bridge.js as a dispatcher: an inbound WebSocket carries an init tree and a list of patches; the bridge runs an eight-case switch on the patch op (text, facts, append, remove-last, reorder, redraw, plugin, lazy) and applies each. An outbound WebSocket carries BROWSER_INPUT and BROWSER_METHOD. A side panel labelled 'not in this file' lists: expression evaluation, state, debouncing, business logic.

The thin bridge: keeping bridge.js dumb on purpose

May 9, 2026

godom's bridge.js builds DOM, applies patches, and forwards events. It does not evaluate expressions, hold state, or make decisions. The constraint is the feature.

A browser-rendered breakout game with rainbow rows of bricks, a paddle, and a ball mid-flight

Breakout, with my phone as the paddle

May 8, 2026

A breakout game built on godom: laptop renders the game, phone is the paddle controller via gyroscope, both connected to the same Go process.

Big Buck Bunny opening frame rendered on a canvas in the godom video player, with -5s, Play, Stop, +5s controls below

A video player that decodes frames in Go

May 7, 2026

Go shells out to ffmpeg, decodes a video into JPEG frames, sends them to a browser canvas. No HTML video tag, no streaming, no codecs in the browser.

A three-tier diagram of JS choices in godom. Tier 0 (default): a Go file with directives and no JS. Tier 1: a small script tag with six lines of scroll-sync code. Tier 2: a plugin file mounting Chart.js with init/update. Arrows show: try Tier 0 first, drop down only if needed.

When to write plain JS in godom (and when not to)

May 6, 2026

godom doesn't ban JavaScript; it pushes it to the edges where it actually pays for itself. Three tiers, one rule, and the trap to avoid.

A 3D solar system rendered in a browser, with the sun glowing in the center, planets orbiting, Saturn with rings, and a sidebar of viewpoint buttons

A 3D solar system in Go, drawn with Canvas 2D

May 5, 2026

I wrote a 3D engine in Go and let the browser draw 2D circles. No three.js, no WebGL, no JS math libraries. Just a list of 2D draw commands per frame.

A diagram of a host HTML page with islands and partials dropped into it: header, counter, display, ticker, and clock islands plus a couple of stateless partial includes. A pink dashed link between the counter and display indicates a shared pointer.

How godom composes: islands, partials, and shared state

May 4, 2026

godom's composition model: stateful islands, stateless partials, slot-based content, and the shared-pointer trick for state across islands.

Claude Code v2 running inside a browser terminal at localhost, showing the welcome screen and slash command list

I put Claude Code in a browser terminal I built in Go

May 3, 2026

I built a browser-based terminal in Go using godom and xterm.js. Then I ran Claude Code inside it. It just worked.

A wire-protocol diagram: a browser pane on the left with an input field and Save button, a WebSocket channel in the center carrying four cyan input frames and a pink method frame to a Go process pane on the right, with a green patch frame returning.

godom's wire protocol: binary patches over WebSocket

May 2, 2026

godom uses binary Protocol Buffers, not JSON, with a deliberate Browser→Go split between input value sync and explicit method calls.

macOS top output rendered inside a browser-based terminal at localhost, with claude processes visible in the process list

Building a UI framework in Go with Claude

May 1, 2026

I built godom mostly with Claude as an implementation partner. Here's what that actually looked like.

Two VDOM trees side by side, previous and next, with the changed node highlighted in pink and the resulting PatchText shown below.

How godom's virtual DOM works

Apr 30, 2026

How godom builds a virtual DOM tree in Go, diffs it against the previous tree, and ships only the patches the browser needs to apply.

A diagram showing an AI agent reading docs/llm-reference.md as context, then producing a Go struct and an HTML template in parallel. The reference doc is shown as a tall stack of sections (Minimal App, Engine API, Island API, Directives, Expressions, Loops, Patterns, Gotchas, Examples Index). An arrow labelled 'one prompt' goes from the agent to a small godom app on the right.

How to use godom with AI agents

Apr 29, 2026

godom ships a docs/llm-reference.md aimed at AI agents writing godom apps. Why that doc exists, what it covers, and what the workflow looks like.