# Julia vs Fortran complaint

**URL:** <https://discourse.julialang.org/t/julia-vs-fortran-complaint/4366>\
**Category:** General Usage\
**Tags:** fortran\
**Created:** [June 20, 2017, 1:09pm UTC](https://discourse.julialang.org/t/julia-vs-fortran-complaint/4366 "2017-06-20T13:09:48Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![ihnorton](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/ihnorton/32/26_2.png) [@ihnorton](https://discourse.julialang.org/u/ihnorton)\
**Post date:** [June 21, 2017, 3:13pm UTC](https://discourse.julialang.org/t/julia-vs-fortran-complaint/4366/22 "2017-06-21T15:13:06Z")

</div>

> [@ExpandingMan](#):
>
> I’m curious, does any of this have to do with the fact that Julia’s compiler is basically a static compiler

Related:

> [@Notes on the Julia compiler (JIT vs static)](https://discourse.julialang.org/t/notes-on-the-julia-compiler-jit-vs-static/4275/2):
>
> in short, it’s a reasonably good static compilier but a terrible JIT (or bascially it’s not a JIT)… By saying that its a static compiler, what I mean is that it does not use any runtimme information to produce optimized code. (Here static information is basically anything in the type domain whereas runtime information being anything in the value domain). The advantage of this approach is that if the code is well writen, the performance will be predictably good, the compile time will also be ve…

---

_[View the full topic](https://discourse.julialang.org/t/julia-vs-fortran-complaint/4366)._