C-like:

• func main() (one-and-only “main” function)
• Same variable scope rules
• No function overloads
• Error handling: Return error, if err != nil, …
  • Extended usage: panic() / recover()

C++-like:

• Variable declaration with auto type (:=)
• OOP features:
  • Structures (with functions)
  • Interfaces: Abstraction io.Reader → Read(...) ...
    • interface{} → any
    • (RTTI?)
• Type switch (switch v := i.(type)) ← Templates
• Function closure (C++? Python?)
• Go 1.18: Generic functions
• public / private via naming conventions

(Java?)-like:

• Strong typing, no implicit conversion (e.g. a := 1 is int, int64(1) is int64)
• “Pointers” (not really) - nullable & mutable reference
  • unsafe.Pointer if you really need (but Cgo = ?)
• GC-language
  • Slice types, map types

(Python?)-like:

• func init()

Feature:

• Goroutines: Low-cost, low overhead logical threads
  • High concurrency (net/http.Server, Caddy)
  • Can’t “kill” easily, context only solves this problem partially
  • No return value (use a channel instead)