One of the most seductive features in modern software engineering is Go's two-character concurrency operator:
go processTask ( task )
Enter fullscreen mode
Exit fullscreen mode
In Python, setting up parallel processing requires heavyweight multiprocessing pools. In Java, managing threads historically meant wrestling with thread pools, context switches, and megabytes of memory per thread. In Node.js, concurrency requires traversing a single-threaded asynchronous event loop.
Then you meet Go. You prefix any function call with go , and the runtime instantly schedules it as an independent concurrent unit. It feels weightless. It feels free.
So developers spawn them everywhere.
You spawn a goroutine for every incoming HTTP request. You spawn another inside a database query. You fire off background goroutines inside loops without second thought.…