Boost Go Development Speed: Master Hot Reload with Fresh, Air, Modd & wgo

Why Go Needs Hot Reload?

Go is a compiled language, and developers often face a repetitive cycle of editing a handler, rebuilding, restarting the service, and refreshing the browser, which slows down development, especially for web projects.

Classic Solution: fresh

Basic Usage

go install github.com/gravityblast/fresh@latest
fresh

By default, fresh monitors .go, .html, and .tpl files in the current directory, runs go build on change, and restarts the application.

How It Works

File change → trigger monitor → go build → stop old process → start new process

Monitoring rules can be customized via runner.conf:

root: .
build_name: runner-build
valid_ext: .go, .tpl, .html
ignored: tmp, assets
build_delay: 600

Other Hot Reload Tools

Air

Installation:

go install github.com/air-verse/air@latest
air

Flexible configuration (custom build commands, exclude directories)

Docker‑friendly development environment

Clearer log output

Air is the “Vite” of Go development.

Modd

A general‑purpose file watcher that can execute arbitrary commands on change.

go install github.com/cortesi/modd/cmd/modd@latest

Example modd.conf:

**/*.go {
  prep: go build -o app .
  daemon: ./app
}

wgo

A minimalist tool with zero configuration.

wgo run main.go

Is This Real Hot Update?

These utilities perform live reload (automatic restart) rather than in‑process code replacement. Go binaries are statically compiled, making true hot swapping difficult; the distinction is crucial for production considerations.

Advanced Exploration for Real Hot Update

1. plugin Package

Go’s plugin package can load .so modules at runtime:

p, _ := plugin.Open("module.so")
sym, _ := p.Lookup("Handler")
sym.(func())()

Plugins can be loaded only once and cannot be unloaded.

Not supported on Windows.

Plugin version must exactly match the main program’s build environment.

2. Subprocess Hot Restart

The main process stays alive while a child process runs business logic; when code changes, the main process spawns a new child and gracefully switches traffic, enabling zero‑downtime deployments.

Implemented via graceful restart, systemd socket activation, etc.

3. Script + WASM Execution Engine

Run business logic through scripts (Lua, JavaScript via Goja) or WebAssembly to avoid restarting the host binary.

vm := goja.New()
_, _ = vm.RunString(`console.log("Hello from new code!")`)

Practical Recommendations

Development Environment

Use air or fresh to speed up iteration.

Configure ignored directories (vendor, node_modules, tmp).

Keep startup logic lightweight to reduce restart time.

Production Environment

Avoid live‑reload tools in production.

Prefer zero‑downtime deployment strategies such as blue‑green, rolling upgrades, or systemd graceful restart.

Do not rely on reflection or dynamic compilation unless absolutely necessary.

Debugging Efficiency

Separate template/static file watching from compilation.

Initialize databases and caches asynchronously.

Log build time and startup latency to drive data‑based optimizations.

Summary

Go hot‑reload tools improve developer experience by automating rebuild and restart, but they are not true in‑process hot swapping. Choose the appropriate tool for your project size, use them in development only, and adopt engineering solutions like graceful restarts for production.