Why pure Go

go-ruby-etcd/etcd reimplements Ruby's etcd in pure Go, with cgo disabled. The slice of Ruby it covers is deterministic and interpreter-independent: given its inputs, the result is a pure function of those inputs — no live binding, no evaluation of arbitrary Ruby. That is exactly the part that can — and should — live as a standalone Go library, separate from the interpreter.

Extracted for reuse, reusable by anyone

• any Go program can import github.com/go-ruby-etcd/etcd directly, with no Ruby runtime;
• the dependency runs the other way — rbgo binds this module as a native module for go-embedded-ruby (the same pattern as go-ruby-yaml), rather than this module depending on the interpreter;
• the behaviour is pinned by a differential oracle against reference Ruby, independent of any one consumer.

Why pure Go matters here

Because the library is CGO-free, it:

• cross-compiles to every Go target with no C toolchain, and links into a single static binary;
• has no dependency on the Ruby runtime — the dependency runs the other way;
• can be differentially tested against the ruby binary wherever one is on PATH, while the cross-arch lanes still validate the library itself.

See Reference for the import path and API.