Re:Understanding the Go Runtime: The Scheduler
by MisterTea on Friday March 13, 2026 @02:04PM
(#47367591)
I find it hard to believe the people who built Go, coming from designing Plan 9 and Inferno, would build a language where it is difficult to swap out a component.
I have this feeling that in their quest to make Go simple, they added complexity in other areas. Then again, this was built at Google, not Bell Labs so the culture of building absurdly complex things likely influenced this.
Re:Understanding the Go Runtime: The Scheduler
by pjmlp on Saturday March 14, 2026 @01:47AM
(#47373726)
The same people refused to support generics for several years, and the current design still has some issues to iron out.
Go also lacks some of Limbo features, e.g. plugin package is kind of abandoned. Thus even though dynamic loading is supported, it is hardly usable.
Having a interface for how it is supposed to behave, a runtime.SetScheduler() or something, but it won't happen.