How does Go's goroutine scheduling differ from traditional OS thread management?

05 Kas 21:45

I'm trying to wrap my head around Go's built‑in scheduler. It maps many lightweight goroutines onto a smaller set of OS threads, but the exact mechanics—whether it's purely cooperative, how preemption is handled, and what triggers a goroutine migration—are still fuzzy to me. Can someone explain the core principles behind the scheduler's decision‑making? Also, what practical tips do you use to avoid hidden performance pitfalls related to scheduling?