# Julia + elixir

**URL:** <https://forum.elixirforum.com/t/julia-elixir/34064>\
**Category:** Discussions\
**Tags:** interoperability, programming-languages, julia\
**Created:** [August 30, 2020, 9:40pm UTC](https://forum.elixirforum.com/t/julia-elixir/34064 "2020-08-30T21:40:40Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![ityonemo](https://forum.elixirforum.com/user_avatar/forum.elixirforum.com/ityonemo/32/11341_2.png) [@ityonemo](https://forum.elixirforum.com/u/ityonemo)\
**Post date:** [August 31, 2020, 3:29pm UTC](https://forum.elixirforum.com/t/julia-elixir/34064/10 "2020-08-31T15:29:49Z")

</div>

> Why should we care? Really. This is all on the “Julia developer” side, not on “Elixir developer” side.

I think if you’re going to want to write an app that you deploy somewhere “in prod”, you are not going to want to struggle with, say virtualenvs. I’ve discussed this with the Julia founders, and honestly, the current Julia deploy strategy for solving this is “just containerize it”. Since Elixir is the more opinionated system, and acting as the ‘orchestrator’ anyways, I think it’s reasonable to take the position that in a mixed language deployment, (that will necessarily have to share container, for example), Elixir should be the “responsible parent” and manage those sorts of things. I _think_ julia has an escape hatch where you can set the deps path, so forcing julia deps into the elixir project tree is “the right thing”.

---

_[View the full topic](https://forum.elixirforum.com/t/julia-elixir/34064)._