>  > Interfaces can be added after the fact if a new idea comes along or 
> for testing—without annotating the original types.
> 
> That's a good step towards the "next language" bit I was talking about 
> earlier. Where unit testing is trivial in the language, or some such.

This is one of my favourit things about Haskell classes [which are 
really interfaces]. You can add them to any type you fancy.

>  > Go's concurrency primitives derive from a different part of the 
> family tree whose main contribution is the powerful notion of channels 
> as first class objects.
> 
> Very nifty. I suspect I'm going to have to look into this more.

I must admit, I'm not sure what this even means. Might be interesting 
though.

"Do not communicate by sharing memory. Instead, share memory by 
communicating. And there is no spoon."

>  > It is practical to create hundreds of thousands of goroutines in the 
> same address space. If goroutines were just threads, system resources 
> would run out at a much smaller number.
> 
> And this.

Lots of languages have light-weight threads, no?

-- 
http://blog.orphi.me.uk/
http://www.zazzle.com/MathematicalOrchid*

Post a reply to this message