4 ms·
I'm doing a lot of concurrent code and Go behaves very well with tens of thousands of concurrent coroutines and network sockets. I couldn't tell the same thing
by fooyc 10y ago
I'm doing a lot of concurrent code and Go behaves very well with tens of thousands of concurrent coroutines and network sockets.
I couldn't tell the same thing about Nodejs, for instance, which is why I tried Go in the first place.
Incidentally my code is much easier to understand, too.
- stymaar 10y agoI personally find the nodejs async much more intuitive than goroutine + synchronous code in it, but this is a highly subjective subject. nodejs use to be pretty annoying when dealing with complex workflow in term of code legibility when it was fully callback-based, but with async/await you get the best of both world IMHO.
- fooyc 10y agoasync/await is a huge improvement over callbacks, but you still have to make sure that everything in your code is async, else you block everything. Also, it doesn't magically works with all functions, the functions have to support async/wait. And it's still less natural than writing sync code