Comment by d33
6 years ago
Pardon the obligatory throwing in of Rust, but it sounds like you were okay switching languages anyway - have you considered Rust as an option? It doesn't have GC and has a very healthy ecosystem (recently with async primitives officially supported by the syntax). It also has the pattern matching you seem to mean. Perhaps it would help you solve your optimization needs? Otherwise, I'd love to hear why it's not a good use case for it since I'm still exploring the language myself.
This kind of promotion creates the tense atmosphere around Rust in the community.
I wonder if anyone has read the linked article?
The overhead of goroutines are well known. The article describes the problem and a solution.
Now someone who got bitten by the overhead of goroutines complains with a (understandable) little bitter tone. He has a good explanation for the issue and why he didn't use Rust but Node.
Citation:
>> I started exploring various options ranging from Rust, Elixir, Crystal, and Node.js. Rust was my second choice, but it doesn't have a good, stable, production ready WebSocket server library yet. Crystal was dropped due to conservative nature of Boehm GC, and Elixir also used more memory than I expected. Node.js surprisingly gave me a nice balance of memory usage and speed.
Then someone didn't seem to have read all the stuff comes around and smartly calls "Use the awesome Rust".
Even as a Rust user myself I get annoyed.
Where is that citation from? Are you quoting from somewhere? I can't find it in the article.
At that point (3 years back) Rust had no good async IO library. All the recent progress in Rust and Tokio now makes it interesting choice.