A few notes on choosing between Go and D for a quick project

Ziad Hatahet via Digitalmars-d digitalmars-d at puremagic.com
Sat Mar 21 21:38:07 PDT 2015

On Wed, Mar 18, 2015 at 1:09 AM, Paulo Pinto via Digitalmars-d <
digitalmars-d at puremagic.com> wrote:

> On Tuesday, 17 March 2015 at 20:50:51 UTC, Bienlein wrote:
>>  Go is only a CSP-like, it isn't CSP. cf Python-CSP and PyCSP, not to
>>> mention JCSP and GPars.
>> I'm not really sure whether this can be put exactly that way. On a
>> machine with 4 GB RAM you can spawn about 80.000 goroutines...
> What about using a JVM with green threads support or Quasar, wouldn't it
> be more comparable?
> --
> Paulo

It seems it is the same issue. From the Quasar user manual (

Fibers are not meant to replace threads in all circumstances. A fiber
should be used when its body (the code it executes) blocks very often
waiting on other fibers (e.g. waiting for messages sent by other fibers on
a channel, or waiting for the value of a dataflow-variable). For
long-running computations that rarely block, traditional threads are
preferable. Fortunately, as we shall see, fibers and threads interoperate
very well.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.puremagic.com/pipermail/digitalmars-d/attachments/20150321/05619372/attachment.html>

More information about the Digitalmars-d mailing list