# How did we get here? (Why is Julia such a messy language?)

**URL:** <https://discourse.julialang.org/t/how-did-we-get-here-why-is-julia-such-a-messy-language/118839>\
**Category:** Internals & Design\
**Created:** [August 31, 2024, 11:57am UTC](https://discourse.julialang.org/t/how-did-we-get-here-why-is-julia-such-a-messy-language/118839 "2024-08-31T11:57:31Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![Tarny\_GG\_Channie](https://avatars.discourse-cdn.com/v4/letter/t/3bc359/32.png) [@Tarny\_GG\_Channie](https://discourse.julialang.org/u/Tarny_GG_Channie)\
**Post date:** [September 1, 2024, 2:04am UTC](https://discourse.julialang.org/t/how-did-we-get-here-why-is-julia-such-a-messy-language/118839/22 "2024-09-01T02:04:24Z")

</div>

I think it would. However, the goal of the package was actually to get a good ECS for Julia. However, it was a hacky bit-dispatch-based ECS, not a full archetypal ECS with lots of features, so, my next ECS would hopefully be that.

However, that next ECS is also where the issue arises, where I think I need to do an unsafe reinterpret and dynamic compilation that would kinda solve some issues, and bring up new ones, such as the compiled code not being GC-ed ever. [Anyone interested in coding a Julia ECS?](https://discourse.julialang.org/t/anyone-interested-in-coding-a-julia-ecs/116587)

---

_[View the full topic](https://discourse.julialang.org/t/how-did-we-get-here-why-is-julia-such-a-messy-language/118839)._