Example: "The company is an entity in the business world." "Entities" is the plural form of "entity" and refers to multiple things or beings. Example: "These entities have different purposes." "The entity" is a specific singular entity being referred to. Example: "The entity responsible for ... More on hinative.com

An entity is just…a thing, usually a thing with some sort of identity or agency. It’s neither positive nor negative. More on reddit.com

It's from a reanalyzed form of the Indo-European copula, which shows up everywhere, including in English is, am, etc. More on reddit.com

I'm new to entity systems, but here's what I know based on what I read. Your entities and components should not have any logic in them. No update methods. Entities are basically nothing. They could be implemented just as a uuid. You just need some way to identify which components belong to an entity. Now components are just data. No update methods either. You just want as simple of a data structure as you can get that describes some meaningful data. For example, position. A position component might have float x and float y and that's it. I think what you may be missing is the concept of systems. You've got entities and you've got components, but your logic (systems) is all still inside those two, which definitely is still OO as you say. If each entity and component knows how to update itself then it's not really a data driven entity system. What you want are systems that iterate over all the same components at once. So you could have a render system that iterates over all entities with a sprite component. The render system looks at the data in the sprite component for each entity and renders a sprite for each entity based on the component data. Sorry if that just made it more confusing. There are many articles written on this topic that explain it better. There was a post the other day that linked to some good articles. Also check out this site for some example entity systems. More on reddit.com