Java: java.util.concurrent
.NET Task Parallel Library
C++ Parallel Patterns Library Threading Building Blocks Click Cilk Plus
D Actors + std.concurrency
Erlang Actors
Scala Actors
Haskell STM
Clojure STM
There are good things about Go, but people should learn other programming languages properly, before doing comparisons.
Among your examples, those that are comparable to goroutines are all for functional languages. There's nothing wrong with functional languages, but it's far from "all mainstream languages".
Fibers are for cooperative multitasking so no parallelism either.
Goroutines are multiplexed as needed onto system threads. http://golang.org/doc/GoCourseDay3.pdf
So they are a bit different, in the spirit of Go: they make for a simple and general solution to both parallelism and concurrency. They combine naturally with channels to give the functionality of OS threads, user threads and fibers.
threading (or CSP) is nothing new conceptually. yes, i agree, the go language has popularized a cheap threading implementation but the same design concepts we've applied to unix processes and posix threads apply to goroutines.
btw, blocks in ruby and generators in python have existed for many years prior to go.
2) One line counter-example to disprove your negative-work argument: goroutines. Also known as: CSP-style concurrency in a procedural language.
I urge you to read up on goroutines. There are quite a few examples on the golang site of how you can use this feature to good effect, examples that would require you to think very differently than if you were in C.
Also, I'd like to point out that the Go project got started because Rob Pike and Ken Thompson grew tired of long build times while working with C++ while at Google. One of Go's objectives is fast compilation times. They are willing to stick to this goal at the expense of complex type systems. This is, if it is anything, not negative work.