# Julia's biggest success\[es\] so far?

**URL:** https://discourse.julialang.org/t/julias-biggest-success-es-so-far/80044
**Category:** Community
**Created:** [April 26, 2022, 10:44am UTC](https://discourse.julialang.org/t/julias-biggest-success-es-so-far/80044 "2022-04-26T10:44:14Z")
**Posts on this page:** 1
**Showing post:** 5

<div class="post-metadata">

### Author: ![NiclasMattsson](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/niclasmattsson/32/21988_2.png) [@NiclasMattsson](https://discourse.julialang.org/u/NiclasMattsson)
#### Post date: [April 26, 2022, 12:48pm UTC](https://discourse.julialang.org/t/julias-biggest-success-es-so-far/80044/5 "2022-04-26T12:48:27Z")

</div>

Here’s a short testimony by @Satvik about a commercial success that I bookmarked last year. It’s (probably deliberately) vague about the details but I found it impressive and convincing nonetheless.

> [@Julia's applicable context is getting narrower over time?](https://discourse.julialang.org/t/julias-applicable-context-is-getting-narrower-over-time/55042/5):
>
> We recently added Julia to our codebase, where we’d previously used Python only for 3 years. This was motivated by optimizing a major process that was a key part of our product and cost $15k/month to run. As you can imagine, we had already heavily optimized it in Python. Everything was using numpy and calling C libraries beneath the hood, but besides that we employed many performance tricks that resulted in very ugly and unpythonic code. We had several very talented engineers look at this, inclu…

---

_[View the full topic](https://discourse.julialang.org/t/julias-biggest-success-es-so-far/80044)._