/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.

>>84
You don't even need to write it in C. "reflect" and "unsafe" generally give very good performance.

The only thing you can't get around is the GC and calling out with FFI won't really help there, the GC is going to run anyway. For example, I have code in C that needs to run during every millisecond, but this is impossible in Go, even if I write that in C and the rest in Go, the GC puts me off schedule whenever it runs.