Sorta unrelated, but I see the existence of engines to also be sort of a problem for Open Source libraries too. They create sort of a maintenance bottleneck. I

Sorta unrelated, but I see the existence of engines to also be sort of a problem for Open Source libraries too. They create sort of a maintenance bottleneck. In other areas where open source is more prevalent (like web dev), there will be virtually a guarantee that someone running into some long-lived issue within a library will try to patch and contribute back, or in the worst case fork it. Because the end users of frameworks/libraries often have the skills needed to patch those libraries. In Games, however, there's fewer and fewer true consumer of libraries, since everything go through engines, and there's a lot of consolidation going on. Also, the popular engines aren't targeted at programmers that could fix the libraries, quite the opposite. That puts a lot of pressure on library maintainers and engine maintainers, as they become the only people able to fix those deeper issues. Bevy of course is a bit lower-level, an others have source-available, but still...