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

2015-09-01 Thread jmh530 via Digitalmars-d-learn
On Tuesday, 25 August 2015 at 05:12:55 UTC, Laeeth Isharc wrote: What's the best reference to learn more about PGAS? I've seen a few presentations, https://www.osc.edu/sites/osc.edu/files/staff_files/dhudak/pgas-tutorial.pdf http://www.inf.unideb.hu/~fazekasg/english/New_Programming_Paradims/

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

2015-09-01 Thread via Digitalmars-d-learn
More info on the Go 1.5 concurrent GC, a classic one: https://blog.golang.org/go15gc

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

2015-08-25 Thread via Digitalmars-d-learn
On Tuesday, 25 August 2015 at 07:21:13 UTC, rsw0x wrote: An option implies you can turn it off, has this changed since the last time I used Rust?(admittedly, a while back) Rust supports other reference types, so you decide by design whether you want to use linear typing or not?

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

2015-08-25 Thread rsw0x via Digitalmars-d-learn
On Tuesday, 25 August 2015 at 07:18:24 UTC, Ola Fosheim Grøstad wrote: 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: [...] Horses for courses ? Eg for Andy Smith's problem of processing trade information of tens of g

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

2015-08-25 Thread 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

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

2015-08-24 Thread via Digitalmars-d-learn
On Monday, 24 August 2015 at 21:20:39 UTC, Russel Winder wrote: The issue here for me is that Chapel provides something that C, C++, D, Rust, Numba, NumPy, cannot – Partitioned Global Address Space (PGAS) programming. This directly attacks the multicore/multiprocessor/cluster side of computing,

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

2015-08-24 Thread Laeeth Isharc via Digitalmars-d-learn
. Of course systems like Numba change the Python performance game, which undermines D's potential in the Python-verse, as it does C and C++. Currently I am investigating Python/Numba/Chapel as the way of doing performance computing. Anyone who just uses Python/NumPy/SciPy is probably not doing

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

2015-08-24 Thread Laeeth Isharc via Digitalmars-d-learn
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 Rus

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

2015-08-24 Thread rsw0x via Digitalmars-d-learn
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

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

2015-08-24 Thread Russel Winder via Digitalmars-d-learn
On Sun, 2015-08-23 at 19:42 +, via Digitalmars-d-learn wrote: > […] > Yes, of course it is, but given it's typical use context I find > it odd that they didn't go more towards higher level constructs. > For me Go displaces Python where more speed is required, though I > wish it was more pyt