shipyard

It's not that it's incompatible, it's that when the ECS is the primary tool for organization, a DOM tree (or scenegraph) is merely one way of iterating over the entities - not the way. This provides tons of benefits, so for example you can also decide to iterate over the entites by shader program and gain significant speedups for graphics processing, or maintain components that roughly sort them by their position in world space for physics and culling or lighting, etc. For a crude analogy, imagine if Document.querySelectorAll() were a zero-cost abstraction, i.e. it ran as fast as iterating over linear memory. In practice this isn't how it turns out with an ECS, but it's much closer and you can get this kind of performance for the "hot path" kind of queries. To add to the sibling comment, there's another wonderful Rust ECS called shipyard[

I'm not replying to detract from your point, because I agree with you whole heartedly that competing ecosystems are not mature enough to dethrown C++ if you're someone who is pragmatic and wants to get things done. C++ has an enormous number of high quality libraries with often no equivalents in competing languages. There are some compelling ECS frameworks emerging in Rust if anyone is interested, though. Legion -- https://github.com/amethyst/legion Hecs -- https://github.com/Ralith/hecs Shipyard -- https://github.com/leudz/shipyard Specs -- https://github.com/amethyst/specs Bevy -- https://github.com/bevyengine/bevy -- not strictly comparable as it's an entire game engine, but it's built around an (imo) more ergonomic fork of hecs. Some benchmarks -- https://github.com/rust-gamedev/ecs_bench_suite