Even better: Julia (although Fortran is pretty good!)

adgjlsfhk1 11 hours ago | parent | next [-]

I translated the jacobi example to julia, and it does seem to address every one of his gripes with Python.

	▲	cbolton an hour ago \| parent [-]
		I think his main point is about strict typing in Fortran. You can add type annotations in Julia but it's almost an anti-pattern if you don't need them e.g. for dispatch. In any case the type annotations in these examples would be quite unnecessary, unlike in Fortran (where as I understand you can at best enable implicit typing but then must use variable names with specific patterns).

▲

QuadmasterXLII 11 hours ago | parent | prev [-]

I love julia, but the default workflow is

Step 1) Write the function using high level abstractions Step 2) Glance over the generated assembly and make sure that it vectorized the way you wanted.

▲

mofeing 11 hours ago | parent [-]

> Glance over the generated assembly and make sure that it vectorized the way you wanted.

Isn't that sth you would also need to do in Fortran? IMO Julia makes this so easy with its `@code_*` macros and is one of the main reasons why I use it.

▲

wtcactus 11 hours ago | parent [-]

In my experience, Fortran compiler is heavily optimized. It competes head to head with C.

Julia’s on the other hand, many times puts out very unoptimized code.

Mind you, last time I looked at Julia was 2-3 years ago, maybe things have changed.

	▲	patagurbon 9 hours ago \| parent [-]
		If you write Julia similar to Fortran, with explicit argument types and for loops and avoiding allocations it shouldn’t be too far off. Fortran IIRC has a few semantics which might make it more optimal in a few cases like aliasing But indeed there are almost certainly less performance surprises in Fortran