The big thing that this allows is for you take the ideas of C++ templates to the extreme. In Julia pretty much every function behaves like a C++ function that is templated on the type of every input. This has the major advantage that it is really easy to write extremely fast generic code. This only works in general though because Julia only has to generate code for the types that actually appear rather than all the type combinations that static analysis can conclude might appear.
In what world did people not know about MPMC queues?
Here are the experiences of Wooga and Activision/Blizzard using it.
https://www.gdcvault.com/play/1016648/Why-Erlang
http://www.erlang-factory.com/upload/presentations/395/Erlan...
Go's concurrency builds on CSP and they're open about it, but it is not just about who came up with it but who made it mainstream and for that Go certainly deserves credit.
That’s because other languages did not need channels as a core language features.
Go does for the same reasons it needs e.g. hashmaps or append as “core language features”: no generics.
As far as I could see, there was one cool thing Go brought to the table, and it’s select {}. That was (and still is, I think) pretty uncommon, though not unheard of (Erlang’s receive is similar, though it has different capabilities owing to different language semantics).
Could you expand on the specific problems that each language avoids?