Re:Thoughts about the cutting-edge of server programming
by necaris on Thursday August 13, 2015 @12:11PM
(#10055235)
The goroutine model allows a lot of tasks to be handled in parallel without the application developer having to worry about it. So, for example, a web framework can have one goroutine per request and scale very well. That is what I would love to see in Rust, although I know it isn't likely right now since a lot of the ecosystem is still maturing.
Re:Thoughts about the cutting-edge of server programming
by RaitoBezarius on Thursday August 13, 2015 @01:19PM
(#10055751)
Oh, I see what you're saying.
Yes, me too. And I may end by giving a try to implement such lib.
Anyway, like you've said, the ecosystem is still maturing. But the more people are interested in Rust, and the more libs we will have.
Re:Thoughts about the cutting-edge of server programming
by khyryk on Thursday August 13, 2015 @10:44PM
(#10058361)
The advantage that Go has with regard to green threads is that the language and its standard library are built around them. There's no easy way to introduce them into a language via a library with the same level of simplicity.
EDIT: Mea culpa, it used to have. (ref. http://stackoverflow.com/questions/29428318/why-did-rust-rem...)
Well, you can always build your own interfaces to achieve a similar result. But why do you need go-routines ?
By the way, at least, Rust tries to handle concurrency the most he can (by analyzing if data race can occur, at compile-time for example).
What do you need more ?