C4 Engine

The best reasons NOT to use the C4 Engine

You prefer code that’s hastily written in order to ship features as quickly as possible. Everybody knows that any good codebase contains a ton of TODOs and FIXMEs. Something that works 90% of the time is good enough.
You have surrendered yourself to the inevitability of frequent crashes in both the engine and the editor. You think you just have to live with it, and there’s no practical way to have anything better.
You don’t mind if it takes 20 minutes to build the engine after a minor source change. You take dozens of coffee breaks every day anyway, and it’s good for the computer to be doing something while you’re away from your desk.
You’re OK with main parts of the engine being based on technology from the 1990s. What worked well then is still the right solution today!
You think having lots of dependencies is good. Every engine should use four different string classes and at least seven 3D vector types, right? And it’s your fault when your code breaks because an external library was updated.
You don’t get mad when wildly exaggerated claims about robustness or scalability turn out not to hold water. It’s OK because those marketing crooks who bent the truth to convince you their product was solid were just doing their jobs!
You enjoy working with a Frankensteinian architecture that was bolted together over two decades without any unifying vision, went through years of neglect by incompetent engineers, and is now held together with duct tape and string.