# A Comparison of Programming Languages in Economics

**URL:** <https://discourse.julialang.org/t/a-comparison-of-programming-languages-in-economics/8966>\
**Category:** Community\
**Created:** [February 10, 2018, 1:04am UTC](https://discourse.julialang.org/t/a-comparison-of-programming-languages-in-economics/8966 "2018-02-10T01:04:10Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![tkoolen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkoolen/32/1603_2.png) [@tkoolen](https://discourse.julialang.org/u/tkoolen)\
**Post date:** [February 10, 2018, 1:28am UTC](https://discourse.julialang.org/t/a-comparison-of-programming-languages-in-economics/8966/4 "2018-02-10T01:28:47Z")

</div>

Did you use the `-O3` and `--check-bounds=no` flags, as well as [rebuild the system image for your architecture](https://docs.julialang.org/en/stable/devdocs/sysimg/)?

Actually, almost half the time is being spent in `log`, which should get a lot better soon by switching from the openlibm implementation to a pure Julia implementation: [https://github.com/JuliaLang/julia/pull/24750](https://github.com/JuliaLang/julia/pull/24750). You can actually already use the new algorithm in 0.6.2 by replacing `log` with `Base.Math.JuliaLibm.log`.

---

_[View the full topic](https://discourse.julialang.org/t/a-comparison-of-programming-languages-in-economics/8966)._