Why you can't use GO! (away from anti-patterns)
summary
Examines situations where Go may not be the right choice by walking through concrete use cases and code examples. Compares Go’s behavior and features to common assumptions, and explains practical differences relevant to high-performance backends, gRPC, and embedded-system contexts.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:56Package Structure
- 6:12What should be part of package
- 8:37Package Hierarchy
- 13:24Specific/Generic Interfaces
- 16:32Error Handling in Go
- 22:49goroutines
- 30:22Pointers
related talks
28mSOLID Go Design
15mJava Devs Go! the Wrong Way 7 Times
44mHow Do You Structure Your Go Apps?
31mGo + Microservices = Go Kit
34mWriting idiomatic Go using Domain Driven Design
44mHow Do You Structure Your Go Apps?
49mExploring domain driven design in Go
26mEffective Patterns and Practices for Polyglot Programming