January 8, 2026
Go vs Rust: Code and Chaos
An Honest Review of Go
Fans cheer speed, critics want enums, and Safari ate the t’s
TLDR: A dev praised Go’s easy concurrency and clean syntax but slammed the lack of enums, weighing a switch back to Rust. Readers split between “Go is a joy” and “enums or bust,” plus comic relief: Safari dropping t’s and a broken [about page](https://benraz.dev/about.html).
A developer’s “honest review” of Go set off a lively chat: big love for built‑in concurrency (doing lots of tasks at once) with channels and goroutines, simple syntax, and interfaces that work without ceremony. But the mood turns spicy over enums—the preset list of options you can lock down in many languages. Go’s workaround with constants felt like “tape on a collapsed bridge,” and the author is eyeing a return to Rust.
Comments turned it into a coding reality show. tombert applauds the elegant channel model but admits, “I don’t have a lot of fun writing Go.” eximius calls the lack of enums the dealbreaker, yet says they’ve learned to live with Go’s warts. On the other side, lagniappe gushes that “Go is a pleasure to use,” praising the rich standard library and fast builds—plus the killer perk that chatbots (LLMs) “get” Go.
Then came the side drama: auggierose swore Safari doesn’t show the t’s, spawning a meme about invisible letters, and dewey popped in to say the about page is broken. Verdict? Go vs Rust is less a war and more a custody battle: joy and speed versus enums and error quirks. Crowd loves the vibes, hates the missing pieces—and keeps receipts.
Key Points
- •Go provides built-in concurrency via Goroutines, channels, and select statements.
- •Go’s type system favors simplicity and composition through struct embedding rather than inheritance.
- •Struct embedding promotes methods and fields, allows overriding, and retains access to original implementations.
- •Types satisfy interfaces implicitly in Go, enabling patterns with interface{} (any) and runtime type switches.
- •Go lacks a native enum type; the common iota-based constant pattern does not enforce exhaustiveness or safety.