Arch.Extended VS DefaultEcs

The most significant new feature is instance support for the Arch.Extended source generated `EventBus`, which allows high-performance event dispatching to static and instance receivers with ordering, inlining, and without boxing or lookups. It's incredibly fast and can also be used outside of Arch.

It recently received a few more Tools and Features to aid development and improve the ECS workflow. E.g. unsafe collections, a ResourceHandler and a static source generated eventbus in Arch.Extended ! :)

Its already matured and already has tons of cool features (even has its own source generator Arch.Extended)! Recently it received a few other cool features like `Bulk Query Operations`, which can be used to bulk destroy or modify entities with an insane performance :)

The source generator of Arch.Extended also had an update and can now generate queries everywhere, is compatible with Unity and Godot and you can mark parameters to pass them through.

Arch even has https://github.com/genaray/Arch.Extended, a source code generator to create systems.... as a contrast to DefaultECS.Analyzer :)

Through Arch.Extended systems can now also be used and even generated through source generation ! :) ( Theres also a sample for monogame ).

For examples I usually turn to GitHub. It has numerous C# game engines. However, I find it easier to figure out implementations myself and use other engines only for API inspiration. There are also several C# ECS such as Entitas and DefaultECS that you can use if you do not want to create you own.