# Changing the Python vs Julia mindset

**URL:** https://discourse.julialang.org/t/changing-the-python-vs-julia-mindset/74777
**Category:** Teaching & Outreach
**Created:** [January 18, 2022, 12:33am UTC](https://discourse.julialang.org/t/changing-the-python-vs-julia-mindset/74777 "2022-01-18T00:33:20Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![CasUpg](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/casupg/32/4392_2.png) [@CasUpg](https://discourse.julialang.org/u/CasUpg)
#### Post date: [January 18, 2022, 12:33am UTC](https://discourse.julialang.org/t/changing-the-python-vs-julia-mindset/74777/1 "2022-01-18T00:33:20Z")

</div>

I made a brief Google search for “Python + Julia” and only received “Python vs Julia” results. Because Python requires C++ for performance, it would be odd to find a “Python vs C++” mentality, at least in DS/ML world. Maybe we need to spread more the “Python and Julia are (or will be) the best friends” motto? Specially when some in python community realize that their future effort [looks a lot like Julia but not exactly](https://dev-discuss.pytorch.org/t/where-we-are-headed-and-why-it-looks-a-lot-like-julia-but-not-exactly-like-julia/276). Perhaps more pyjulia kind thrust is the best formula for the consolidation of Julia?

In the future, will we speak of "the two languages Joy " instead of “the two languages problem”? (it’s joke) Any thought?

---

<div class="post-metadata">

### Author: ![jzr](https://avatars.discourse-cdn.com/v4/letter/j/eb9ed0/32.png) [@jzr](https://discourse.julialang.org/u/jzr)
#### Post date: [January 18, 2022, 12:39am UTC](https://discourse.julialang.org/t/changing-the-python-vs-julia-mindset/74777/2 "2022-01-18T00:39:54Z")

</div>

If Julia could make libraries, we could start making python packages with Julia code, so it would be “Python + Julia” vs “Python + C++”.
