Slick Forums

What are your thoughts? Where one is better then other one?

_________________
Blog | Last game Gravity Duck tribute | In progress Gravity Duck tribute

I think it's more a question of preference.

Apollo is perhaps more of "traditional" solution for a entity/component framework, where you have logic with your components. Some may be more convenient with this, and most will probably get started quicker with Apollo because it builds on existing preconceptions about programming.

Artemis on the other hand is more "untraditional" because it's not as object-oriented like Apollo and is aspects/systems oriented, and is perhaps more experimental and thus not as proven in design although it's pretty well optimized and decently smart. Artemis is something like a introductory framework to this world of dealing with components as pure data and systems as aspects that process or deal with that data. People may have trouble of knowing exactly how to write their games with Artemis because it requires different thinking.

I don't really think comparing the two is fair, they are naturally different. I think Artemis is more abstract because it doesn't provide you with things like rendering, like Apollo. I'm pretty proud of Artemis, because I put a lot of brain into it, and I don't intend for Apollo to be some sort of replacement, because it's a totally different ideology, and I will also be developing Artemis further.

Good to hear that! I like Artemis, wouldn't want to miss it!

I guess this thread has already been satisfactorily attended to, but for what it's worth:

When I first started exploring component-based design, I coded my own framework (because, honestly, I didn't find anything readily available). Although my components-with-logic approach provided a few blissful eureka moments, in the end I felt kinda cheated; the final design becomes slightly less hierarchical, though it still feels very much like OO in new clothing. It might be easier to grasp when coming from an OO background, and, overall it has a more pluggable feel to it (such as, I miss being able throw in a pair of telnet+scripting components as a supplement to conventional debugging, or just being able to easily generate architectural component diagrams from code etc).

With artemis, my systems/components tend to be more specialized to the task at hand, mainly because they're exquisitely trivial to write. I guess some folks prefer writing more generalized systems, but to me, the strength of Artemis is being able to easily make changes to an existing design, without causing ripple effects. Components-with-logic do that to some extent, but nowhere near as good as an entity-system.