# Anyone interested in coding a Julia ECS?

**URL:** <https://discourse.julialang.org/t/anyone-interested-in-coding-a-julia-ecs/116587>\
**Category:** Community\
**Created:** [July 3, 2024, 1:46pm UTC](https://discourse.julialang.org/t/anyone-interested-in-coding-a-julia-ecs/116587 "2024-07-03T13:46:54Z")\
**Posts on this page:** 1\
**Showing post:** 5

<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, 5:55am UTC](https://discourse.julialang.org/t/anyone-interested-in-coding-a-julia-ecs/116587/5 "2024-09-01T05:55:43Z")

</div>

Anyway… let’s continue the discussion here, where it’s more relevant.

> [@How did we get here? (Why is Julia such a messy language?)](https://discourse.julialang.org/t/how-did-we-get-here-why-is-julia-such-a-messy-language/118839/27):
>
> - Make it work
> - Make it right
> - Make it fast

The issue is that if you just try to make it work without trying to make it fast at all, you could store every entity as a dictionary and store every update as a function that checks each element whether or not they have the right components. The reason you need a complex ECS is because you need it to be fast, otherwise, you could’ve stuck to OOP or sloppily implemented ECS.

---

_[View the full topic](https://discourse.julialang.org/t/anyone-interested-in-coding-a-julia-ecs/116587)._