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

[deadalnix via Digitalmars-d]

On Saturday, 14 March 2015 at 03:12:39 UTC, Andrei Alexandrescu 
wrote:
> On 3/13/15 5:54 PM, deadalnix wrote:
>> On Saturday, 14 March 2015 at 00:34:35 UTC, Ziad Hatahet wrote:
>>> On Fri, Mar 13, 2015 at 6:45 AM, Russel Winder via 
>>> Digitalmars-d <
>>> digitalmars-d at puremagic.com> wrote:
>>>
>>>> The removal of shared memory multi-threading in favour of 
>>>> using
>>>> processes and channels should never be underestimated as a 
>>>> Really Good
>>>> Thing™ that other native code languages (*) have failed to 
>>>> do anything
>>>> about. Thus Go wins, others lose.
>>>>
>>>
>>> Except that Go does not really remove shared memory 
>>> multithreading; it is
>>> still possible to get data races (which is why they have a 
>>> race
>>> detector).
>>> They provide channels, but nothing is preventing races other 
>>> than
>>> convention. On the other hand, Rust (a native code language) 
>>> offers a
>>> much
>>> superior solution, with compile-time enforcement of data 
>>> sharing.
>>>
>>> --
>>> Ziad
>>
>> How very true, but, by the time you run into data races, you 
>> are pretty
>> much commited to go.
>>
>> Sad.
>
> I'm surprised Russel fell for it. -- Andrei

Don't be surprised, because, by the time you run into data races, 
you are pretty much committed to go.