Also, koota has really nice React bindings. My UX is all React/Three.js, and maintaining the necessary bindings myself sounds like a pain.

Tempting, but I've learned enough about various ECS implementations to be wary, since there is a lot to get right, and I know I'll need more advanced features like relations and change detection. I also find it hard to reason about performance when the backend is JS running in the browser.

Context: I'm writing custom bindings for a TypeScript library (koota) that went a bit overboard on the advanced features of TypeScript's type system, so Glutinum can't really comprehend it.

I'm not sure which thing I'd rather maintain -- my own ECS, or this wrapper (assuming it ever compiles). 2/2

I’m sure a big part of that comes from having the ability to make problems go away with money, thus never developing the personal capacity to solve problems oneself.

It’s awfully convenient for CBC to leave out the fact that many Gitxsan oppose this project.

Does Bevy support relations?

I’m also getting my feet wet with ECS, but in the context of React/TypeScript using koota, which supports relations. They’re proving useful for modeling complex hierarchical structures.

ECS takes getting used to, but I like the flexibility and separation of concerns.

If you keep this up, people are going to start asking you to run for public office.