Consider going DOTS-like? about taro HOT 4 CLOSED

True ECS frameworks, like ecsy, was something I definitely looked at while working on Taro. I went for the traditional OOP because it felt like the easier route -- both in implementing and utilizing the library. I'm definitely open to going DOTS-like (maybe another branch?), but that would require a lot more research on my end since Taro doesn't have a lot of contributors.

from taro.

I also wonder if you maybe consider porting Taro to TypeScript and using things like decorators and reflect-metadata on component classes in order to specify the schematic metadata you need for the editor.

I would love to see Taro move towards DOTS and towards type-safety. Some TypeScript ECS I think are quite good are Tick-Knock https://github.com/mayakwd/tick-knock and Nopun https://github.com/grebaldi/nopun-ecs. Maybe we could use them as inspiration, add reflect-metadata ontop, and come out with a type-safe DOTS-like threejs ECS that is still editor amenable?

from taro.

I think porting Taro to TypeScript would be a separate branch, similar to the DefinitelyTyped repo for threejs. At the moment, I don't plan to port Taro to TypeScript, but I'd be open to others contributing to a TypeScript branch.

from taro.

Maintaining typings is different than porting the codebase to TypeScript. With typings we'd be constantly trying to keep them in sync with the codebase and that sounds Sisyphean. On the other hand, by porting the codebase to TypeScript, the codebase itself becomes the source of typings. Anyway thanks for being straightforward about it.

from taro.