You can look at the repository to see the differences. The troubleshooting abilities of the program are far superior to lutris already, My experience with lutris is you run the install script, attempt to run the game, it doesnt work and fails silently, the logs are empty, and even if you do capture the logs, the core issue often isn't clear.
1. It manages memory through deterministic ownership rules and optional arena allocation. Pointers never outlive the allocator that created them, and the compiler performs lifetime checks to prevent use-after-free or double-free errors.
2. Axe does not use C++-style RAII. It employs deterministic cleanup through defer, which allows resources to be released predictably. Also, objects allocated inside an arena are freed as a group when the corresponding arena is destroyed.
3. Not yet. There is an overload system currently: