That is not quite what the article is talking about. There's a bit of a terminology collision here. What the article is talking about is not Data-Oriented Desi

That is not quite what the article is talking about. There's a bit of a terminology collision here. What the article is talking about is not Data-Oriented Design, the practice of organizing your data for efficient processing. It's proposing a separate (but not incompatible) concept of organizing your code for easier maintainability. For example, the sample code (which appears to be JavaScript) is not doing ECS at all. It's almost exclusively doing the data modeling by creating one heterogeneous map per entity.