# Ensure Julia is used to its full power

**URL:** <https://discourse.julialang.org/t/ensure-julia-is-used-to-its-full-power/51155>\
**Category:** New to Julia\
**Tags:** question, first-steps\
**Created:** [December 3, 2020, 12:02am UTC](https://discourse.julialang.org/t/ensure-julia-is-used-to-its-full-power/51155 "2020-12-03T00:02:23Z")\
**Posts on this page:** 1\
**Page:** 6

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [December 11, 2020, 12:15pm UTC](https://discourse.julialang.org/t/ensure-julia-is-used-to-its-full-power/51155/102 "2020-12-11T12:15:27Z")

</div>

> [@Undercover](#):
>
> if required dig deeper into what’s happening and still be in Julia code, but in the end, Julia will also be written in C, so if somebody goes too deep they might say the same thing some of you are saying here about Python

I have been using Julia since 0.3, and never had to write or understand a single line of C in the process.

Also, I think it should be understood that Julia users comparing Julia to Python are not aiming to bash Python. The design of Julia _benefited_ a lot from the experience accumulated with Python, especially when it comes to performance and optimization. The lessons learned with 3 decades of Python made Julia possible by improving on it.

[Previous page](https://discourse.julialang.org/t/ensure-julia-is-used-to-its-full-power/51155.md?page=5)