Role of D in Python and performance computing [was post on using go 1.5 and GC latency]

[via Digitalmars-d-learn]

On Tuesday, 25 August 2015 at 05:09:56 UTC, Laeeth Isharc wrote:
> On Monday, 24 August 2015 at 21:57:41 UTC, rsw0x wrote:
>> On Monday, 24 August 2015 at 21:20:39 UTC, Russel Winder wrote:
>>> For Python and native code, D is a great fit, perhaps more so 
>>> that Rust, except that Rust is getting more mind share, 
>>> probably because it is new.
>>
>> I'm of the opinion that Rust's popularity will quickly die 
>> when people realize it's a pain to use.
>
> Horses for courses ?  Eg for Andy Smith's problem of processing 
> trade information of tens of gigs where Python was choking, I 
> guess nobody in their right mind would use Rust.

I don't think there is much difference between C, D or Rust in 
terms of computing. The core semantics are similar. With Rust you 
have the additional option of linear type checking.

But Rust programmers of course want to use idiomatic linear 
typing as much as possible and that makes designing graph-like 
structures a challenge.