ECS game engine
been messing around with Odin lately and honestly it feels like it was kinda made for ECS-style stuff. no hidden allocations, easy to reason about memory layout, no OOP nonsense getting in the way. but I don't have much real experience writing engines so idk if I'm just pattern matching because the language "feels" data-oriented.
anyone actually built something like this in Odin? curious how it goes in practice, especially around
- component storage / query stuff without generics being a pain
- whether manual memory management actually becomes annoying at scale or if it's fine
- how it stacks up against Rust+Bevy speed/ergonomics wise once things get complex
thinking of not reinventing the wheel and instead basically porting bevy's ideas over (archetypes, scheduler etc) instead of designing my own ECS from scratch. is that a dumb idea? rust and odin are pretty different (ownership vs manual mem, traits vs whatever odin has) so maybe a direct port just doesn't translate well and I'd be fighting the language the whole time.
if anyone's tried this or has war stories/gotchas before I waste a month on it, let me know
