# I just decided to migrate from Python+Fortran to Julia as Julia was faster in my test

**URL:** <https://discourse.julialang.org/t/i-just-decided-to-migrate-from-python-fortran-to-julia-as-julia-was-faster-in-my-test/61188>\
**Category:** Community\
**Tags:** fortran, performance, python, tullio, loopvectorization\
**Created:** [May 15, 2021, 4:44am UTC](https://discourse.julialang.org/t/i-just-decided-to-migrate-from-python-fortran-to-julia-as-julia-was-faster-in-my-test/61188 "2021-05-15T04:44:41Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![tkf](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkf/32/17635_2.png) [@tkf](https://discourse.julialang.org/u/tkf)\
**Post date:** [May 16, 2021, 4:56am UTC](https://discourse.julialang.org/t/i-just-decided-to-migrate-from-python-fortran-to-julia-as-julia-was-faster-in-my-test/61188/11 "2021-05-16T04:56:47Z")

</div>

FYI `@inbounds` should go inside of closure-creating macros like `@threads` and `@spawn` (like leandromartinez98’s `eval_exp_tweaked_4_parallel`). Ref: [What is the cause of this performance difference between Julia and Cython? - #4 by tkf](https://discourse.julialang.org/t/what-is-the-cause-of-this-performance-difference-between-julia-and-cython/58886/4)

(Personally, I believe `@inbounds` scope should be as small as possible in general. Putting it outside a macro call is especially worrisome as you usually don’t know what code the macro will generates.)

---

_[View the full topic](https://discourse.julialang.org/t/i-just-decided-to-migrate-from-python-fortran-to-julia-as-julia-was-faster-in-my-test/61188)._