# Julia written in Julia?

**URL:** <https://discourse.julialang.org/t/julia-written-in-julia/25781>\
**Category:** Internals & Design\
**Tags:** question\
**Created:** [June 27, 2019, 10:31pm UTC](https://discourse.julialang.org/t/julia-written-in-julia/25781 "2019-06-27T22:31:17Z")\
**Posts on this page:** 1\
**Showing post:** 37

<div class="post-metadata">

**Author:** ![tkoolen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tkoolen/32/1603_2.png) [@tkoolen](https://discourse.julialang.org/u/tkoolen)\
**Post date:** [July 6, 2019, 5:02am UTC](https://discourse.julialang.org/t/julia-written-in-julia/25781/37 "2019-07-06T05:02:39Z")

</div>

I tend to gravitate towards templated C++ code because of an ideal of expressing a generic concept in only a few lines, but I definitely recognize the verbosity / general lack of readability of templated C++ code and its (anti?) patterns (e.g., CRTP). That’s what attracted me to Julia in the first place.

I think the concept of “C where possible, ‘basic’ C++ where necessary for LLVM interop” makes sense for Julia from the point of view of making it relatively easy to contribute + performance, and given the core developers’ experience.

> [@jpsamaroo](#):
>
> There are open PRs to try replacing the femtolisp parser with CSTParser, so that’s something to look forward to

I think this is a very important development, if just because of tighter integration between the core language and IDEs (see also this thread I started a while back: [Talk by Anders Hejlsberg on interplay between editors and compiler](https://discourse.julialang.org/t/talk-by-anders-hejlsberg-on-interplay-between-editors-and-compiler/11570)).

---

_[View the full topic](https://discourse.julialang.org/t/julia-written-in-julia/25781)._