> "This would be a lot easier if we didn't have malloc()/free()", basically. Well, not really. It's just some libraries like YamlDotNet copy waaaay more than n

> "This would be a lot easier if we didn't have malloc()/free()", basically. Well, not really. It's just some libraries like YamlDotNet copy waaaay more than needed and it shows in serialization. They mostly minimized calling YamlDotNet, but true solution would be a zero copy parser. Other issue was HashSet operation like Clear had huge impact. Think they replaced those with arrays. Third issue was something about flecs and archetype ECS. I don't know if it was a jest, but they mentioned changing GC layout or rewriting GC. Points is, they now face a steep performance cliff. The only way out of it is through sheer effort. So no, it's not anti-GC religion. Some domains and GC really badly mix.