[Numpy-discussion] Numpy performance vs Matlab.
Wed Jan 7 12:52:43 CST 2009
On Wed, Jan 7, 2009 at 1:32 PM, Sturla Molden <firstname.lastname@example.org> wrote:
> On 1/7/2009 6:56 PM, Christopher Barker wrote:
>>> So for simple loops python looses, but for other things, python wins
>>> by a huge margin.
>> which emphasizes the point that you can't write code the same way in the
>> two languages, though I'd argue that that code needs refactoring in any
> Roux example would be bad in either language. Slices ('vectorization' in
> Matlab lingo) is preferred in both cases. It's just that neither Matlab
> nor Python/NumPy was designed to be used like Java. For loops should not
> be abused in Python nor in Matlab (but Matlab is more forgiving now than
> it used to be).
> Sturla Molden
> Numpy-discussion mailing list
I'm missing name spaces in matlab. everything is
from path import *
and it's more difficult to keep are larger project organized in matlab
than in python.
But, I think,
matlab is ahead in parallelization (which I haven't used much)
and learning matlab is easier than numpy. (dtypes and broadcasting are
more restrictive in matlab but, for a beginner, easier to figure out)
More information about the Numpy-discussion