Processes and Channels, cf. goroutines.

[Bienlein]

On Monday, 3 March 2014 at 14:27:53 UTC, Sönke Ludwig wrote:

> Just out of curiosity, what did you miss in vibe.d regarding 
> fiber based scheduling?

There is something else I forgot to mention. One scenario I'm 
thinking of is to have a large number of connections like more 
than 100.000 I want to listen on. This results in a situation 
with blocking I/O for all those connections. Fibers in D are more 
like continuations that are distributed over several kernel 
threads. The way Sean Kelly has implemented the FiberScheduler a 
fiber is invoked in case it receives an item like data through 
the connection it serves as in my scenario. At least this is the 
way I understood the implementation. So I can have like 100.000 
connections simultanously as in Go without having to use Go (the 
Go language is too simple for my taste).