On 13/11/2013 19:30, Daniel Micay wrote:
It's known that M:N scheduling is a viable way of building a socket
server. I'm only questioning whether it's worth making compromises for
every other use case to micro-optimize context switches out of socket
servers and make them scalable on platforms with poor support for the
1:1 threading model (OS X).
I take great issue with some of what you write:
- there is an assumption that lightweight is useful primarily for
'socket servers'
- you say things are not problems, if they are not problems on Linux,
for some
unspecified version of Linux.
For the former: you seem to disregard the benefits that actor-based systems
with very lightweight tasks can have. For the latter, well, not
everyone uses Linux,
all the time, and I had though Rust was supposed to be portable, and by
that I
would expect good performance to be portable as well as syntax.
I had high hopes of Rust having lightweight segmented stacks and precise
per-task
GC and portability too. Sort of Erlang with type safety and AOT
compilation with a
sane model.
But now much of this seems abandoned or clearly a long way out and it is
becoming
more like C++ with some functional bits, and I can get that with Scala
and F# now.
James, in sadness.
_______________________________________________
Rust-dev mailing list
Rust-dev@mozilla.org
https://mail.mozilla.org/listinfo/rust-dev
