4 ms·
I'm guessing he means http://en.wikipedia.org/wiki/Entity_component_system http://en.wikipedia.org/wiki/Entity_component_system While some big games have used
by jamii 13y ago
I'm guessing he means http://en.wikipedia.org/wiki/Entity_component_system http://en.wikipedia.org/wiki/Entity_component_system
While some big games have used it, a lot more games are still stuck on class hierarchies.
- munificent 13y agoThose aren't orthogonal. There's a pretty wide design space for component systems. Lots of games use "components", where game entities are split into pieces for different game domains (rendering, AI, etc) without going all the way down the entities/components/systems path. It is true that most games don't use MVC. I think that's because MVC isn't a good fit for games. It seems to work fine for business apps, though more experimentation is always good.
- peterhunt 13y agoI think swannodette's post is less about MVC and more about declarative manipulation of the DOM. As long as you have a function somewhere that creates that representation and a way of handling events you can use any sort of architecture you want.
- phillmv 13y agoThe web's headed that way as well, we just call them services. That said, I'm not sure why MVC is inappropriate for component intra architecture. I love how different programming communities never talk to each other.