While I can't comment too strongly on the performance aspects of this article on Green Thread performance, there's a paragraph at the beginning that caught my attention:
If one looks closely enough at green threads, such as Go's 'go' statement, it's not hard to realise that they are really a flow control mechanism similar to 'if', 'for' or 'while' statements. Where 'if' allows you to skip a block of code, green threads give you a way to easily switch between different points of execution. Very much like 'if' or 'while' they are glorified jump statements.
To which my initial reaction was, "Yes, that was covered in Chapter 3 of Lisp In Small Pieces."
In fact, everything you need to know about control flow is covered in Chapter 3 of Christian Queinnec's amazing, now 20-year-old book. In terms of control flow mechanisms for programs, we haven't invented anything new since that book came out. If you've read Lisp in Small Pieces and Why Functional Programming Matters, you've read everything you need to create modern, composable, performant software. The biggest insight in LiSP is that all of these mechanisms for code parallelization, threads, communication modes, concurrency, and so forth are exactly the same as "if"; everything else is (important) details, like performance, but the underlying nature of programming is unchanged: there is one and only one instruction that matters: conditional jump. All else is commentary.
Necessary commentary. Abstractions necessary to constraining the development process in order to eliminate error. But still, commentary; when someone expresses "surprise" that Go's go is semantically similar to if, it tells me that they've never taken, or somehow missed, the fundamentals taught in their CS program.