Browser extensionPublished
Data Explorer for Force.com
A Chrome extension for running SOQL and SOSL queries directly against Salesforce with no intermediate server.
Tags / JavaScript
JavaScript
Projects
Go UI frameworkActive
godom
Local apps in Go, with a browser UI. One binary, shared state across tabs, and no separate JavaScript frontend.
13 connected posts
Static site generatorArchive
Nirman
A flexible Node.js static site generator I built when existing tools felt too rigid and too tied to someone else's content model.
2 connected postsPosts
Realtime
How WebSockets actually work, and what bites you
How WebSockets work: the handshake, the frames, and the gotchas, learned from running real systems over them.
Go
How to use godom
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.
Go
The thin bridge: keeping bridge.js dumb on purpose
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.
Go
Breakout, with my phone as the paddle
A breakout game built on godom: laptop renders the game, phone is the paddle controller via gyroscope, both connected to the same Go process.
Go
A video player that decodes frames in Go
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.
Go
When to write plain JS in godom (and when not to)
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.
Go
A 3D solar system in Go, drawn with Canvas 2D
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.
Go
How godom composes: islands, partials, and shared state
godom's composition model: stateful islands, stateless partials, slot-based content, and the shared-pointer trick for state across islands.
Go
I put Claude Code in a browser terminal I built in Go
I built a browser-based terminal in Go using godom and xterm.js. Then I ran Claude Code inside it. It just worked.
Go
godom's wire protocol: binary patches over WebSocket
godom uses binary Protocol Buffers, not JSON, with a deliberate Browser→Go split between input value sync and explicit method calls.
Go
How godom's virtual DOM works
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.
Go
Why I built godom
I kept needing a UI for local Go tools and hating every option. So I built a framework where Go owns the DOM and the browser is just a screen.