/prog/s opinion on Go

You know, the google thing.  Personally I'm a bit excited for a compiled python-like C language.  It's going to take for fucking ever for it to become useful, though, especially with google's slow and steady attitude.  I could see it catching on though kind of like python did.

>>61
Go has multiple return.

Really, it doesn't have to be as fast as C. Close enough is good enough. 80% is pretty good for a debut with a to-be-fixed collector.

What you *should* be worried about is GC-induced latency. The GC being implemented claims to pause for only 1ms, which is usable. People are already writing Java for embedded "realtime" systems you know, and people are even paying good money for those devices.