@kat I don’t like Golang much either, but I am not a programmer. This little site, Go by example might explain a thing or two.

@bender What's not to like? 😅

@prologic what’s to like? :-P

@bender Here's a short-list:

• Simple, minimal syntax—master the core in hours, not months.
• CSP-style concurrency (goroutines & channels)—safe, scalable parallelism.
• Blazing-fast compiler & single-binary deploys—zero runtime dependencies.
• Rich stdlib & built-in tooling (gofmt, go test, modules).
• No heavy frameworks or hidden magic—unlike Java/C++/Python overhead.

One of the nicest things about Go is the language itself, comparing Go to other popular languages in terms of the complexity to learn to be proficient in:

• Go: 25 keywords (Stack Overflow); CSP-style concurrency (goroutines & channels)
• Python 2: 30 keywords (TutorialsPoint); GIL-bound threads & multiprocessing (Wikipedia)
• Python 3: 35 keywords (Initial Commit); GIL-bound threads, asyncio & multiprocessing (Wikipedia, DEV Community)
• Java: 50 keywords (Stack Overflow); threads + java.util.concurrent (Wikipedia)
• C++: 82 keywords (Stack Overflow); std::thread, atomics & futures (en.cppreference.com)
• JavaScript: 38 keywords (Stack Overflow); single-threaded event loop & async/await, Web Workers (Wikipedia)
• Ruby: 42 keywords (Stack Overflow); GIL-bound threads (MRI), fibers & processes (Wikipedia)

Ultimately, Go sits in the sweet spot on the complexity vs performance chart:

• Minimal syntax & concepts → low learning curve
• Compiled speed → high throughput
• Built-in CSP concurrency → scalable by default

See Rob Pyke's presentation on Expressiveness of Go