python vs d

[Russel Winder via Digitalmars-d]

On Mon, 2014-04-28 at 14:15 +0000, Chris via Digitalmars-d wrote:
[…]
> E.g. an algorithm for signal processing. Python is fine for 
> prototyping, but if you want your algorithms to work in a real 
> world app at real time, you'll have to rewrite it in C/C++, D or 
> whatever. I've adopted the policy (where ever applicable) to use 
> D straight away. It's just not worth it to develop something in 
> Python and rewrite it in D later. I don't see the benefits of 
> writing in Python, only drawbacks in the long run.

Certainly for signal processing algorithms where speed, concurrency and
parallelism are orders of the day, I would choose D or Go from the
outset. I wouldn't choose to use Python for this, but many people do,
including the folk I am off to do a Python workshop for in a couple of
weeks. Their environment is one in which Python is the only option (long
story), so they write in Python and then optimize by using Cython on the
CPU intensive codes. This actually works very well for them.

-- 
Russel.
=============================================================================
Dr Russel Winder      t: +44 20 7585 2200   voip: sip:russel.winder at ekiga.net
41 Buckmaster Road    m: +44 7770 465 077   xmpp: russel at winder.org.uk
London SW11 1EN, UK   w: www.russel.org.uk  skype: russel_winder