@mentalguy @bascule I *think* (although i don't have data in front of me) that's the most common problem - fear of setting M very high
@raggi @mentalguy per Rust, supporting both M:N and "N:1" seems pragmatic. I would guess but haven't seen confirmed that Go is headed there
-
-
@bascule@mentalguy er, i shoudl be clear, goroutines do get pre-empted when m > 1, but they don't free m's until they coopt.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule@mentalguy even though the runtime currently doesn't support thatThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule@mentalguy but i could see it adopting user level scehduling eventually, as the language spec assumes pre-emptive goroutinesThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
@bascule@mentalguy go sort of has an advantage in the way that it wraps syscalls, there's less abstraction in confilict...Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.