3 ms·
> The only thing it get's write is the excellent microthreads and CSP implementation. No at all. It's very far from even remotely decent implementation, the in
by zzzcpan 10y ago
> The only thing it get's write is the excellent microthreads and CSP implementation.
No at all. It's very far from even remotely decent implementation, the interface is too inconsistent and full of implicit behaviors and the performance is an order of magnitude slower than anything acceptable. But anyone actually using it already knows..
- the_duke 10y agoI admit we dropped Go before getting to production, with any kind of performance requirements. I liked the goroutine related apis though. What I remember being PAINFULLY slow is reflection. Which is very inconvenient for certain tasks (building objects from db queries, (json) serializing,...). Macros could help here, but alas, code generation is the only alternative available. Which I'm not a fan of. --- What's are your gripes with Gos CSP?
- themihai 10y agoThe reflection is slow indeed but most of the time you can use caching to improve it(at least that was my case). I like Go a lot but I must admit that some features would make my life easier and perhaps the language more expressive too(i.e. variant types). If that is not good enough you can use code generation(last resort)