Heh, found out today that Rust's async model is turning out to be pretty close to how Node works. This example spawns up 4 event loops, and round-robins requests between them. Like with require('cluster')! https://github.com/tokio-rs/tokio-core/blob/master/examples/echo-threads.rs …
-
Show this thread
-
My hope is that this might be done more neatly in the future. It'd be cool if it became closer to Golang's threading model. Golang doesn't make use of round-robin to assign work. Instead it knows what the load of each core is and schedules tasks accordingly.
2 replies 0 retweets 1 likeShow this thread -
Also: a lot of complexity here seems to come from working around OS shortcomings. What if operating systems had a light threading abstraction built in? Would that make sense even? There seem to be many people working on this problem in parallel. So maybe?
1 reply 0 retweets 0 likesShow this thread -
Tldr: I'm impressed by Go's threading model, and wish Rust could schedule work in the same way
1 reply 0 retweets 0 likesShow this thread -
Replying to @yoshuawuyts
Obligatory mention of erlang style concurrency aka what if fork() was free?
1 reply 0 retweets 1 like
Hah, yeah! Oh man, I conceptually like Erlang a lot!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.