# Julia has ruined my work experience

**URL:** <https://discourse.julialang.org/t/julia-has-ruined-my-work-experience/116556>\
**Category:** Offtopic\
**Tags:** appreciation\
**Created:** [July 3, 2024, 1:24am UTC](https://discourse.julialang.org/t/julia-has-ruined-my-work-experience/116556 "2024-07-03T01:24:17Z")\
**Posts on this page:** 1\
**Showing post:** 14

<div class="post-metadata">

**Author:** ![Satvik](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/satvik/32/20486_2.png) [@Satvik](https://discourse.julialang.org/u/Satvik)\
**Post date:** [July 3, 2024, 4:34pm UTC](https://discourse.julialang.org/t/julia-has-ruined-my-work-experience/116556/14 "2024-07-03T16:34:29Z")

</div>

> [@kapple](#):
>
> do your more recent projects still find their footing in Python? Or do you now use Julia at work as the main language? Asking particularly because the pain points you illustrated in your talk were in the Python-Julia interfacing.

We use Julia for almost all numeric/data-oriented stuff now, and have moved a lot of the Python code to Julia. We still use Python for other parts of the codebase, like connecting to exchanges and doing the actual trading. At this point 99% of new code I write is Julia, and for the company as a whole it’s about 50-50. The performance differential has become even more ridiculous, an experiment that used to cost ~$125 to run now costs ~.33 cents, and most of those improvements wouldn’t really have been possible in Python.

Interop is still a bit painful, in particular because any Python code called through Julia is not thread-safe, and even forcing Python code to run on the main thread doesn’t solve all the issues.

---

_[View the full topic](https://discourse.julialang.org/t/julia-has-ruined-my-work-experience/116556)._