artemis-odb VS ashley

Probably this https://github.com/junkdog/artemis-odb

To my knowledge Artemis-Odb ( https://github.com/junkdog/Artemis-odb ) is one of the faster Java ECS implementations. It might be fun and interesting to benchmark against it. Although Artemis-Odb has a different and larger scope and is probably not fully comparable.

I've tinkered with Artemis-odb in a libgdx project, but its honestly starting to feel bloated. I've also tried Ashley, but Artemis seems to be the gold standard for java ECS. It could use a good contender to shake things up.

Modern fork of it for those who are curious: https://github.com/junkdog/artemis-odb

In artemis there is the same concept, with ComponentMapper, maybe can help you: https://github.com/junkdog/artemis-odb/blob/develop/artemis-core/artemis/src/main/java/com/artemis/ComponentMapper.java

Ashley Entity System is an Entity System library that’s managed under the LibGDX organization and is well-suited for game development. It depends on LibGDX utility classes. Entity systems provide a different way to manage data and functionality towards large sets of objects without having to make the object classes rich with inheritance. Utilizing Ashley might be a helpful approach for those looking for an object modeling approach like Unity provides, but with the scope of a framework instead of the game engine.

> I have tasked my self with reimplementing a really basic version of my game using Ashley ECS. It is actually going seemingly well so far, but I have some general ECS questions as well as some Ashley specific ones I was hoping to get some RogueLikeDev perspective on before I get too deep into it.

Here's the ECS library that I've been using.