The Exigent Duality
Unexpectedly Difficult - 11:49 CST, 5/16/20 (Sniper)
I've been on projects like this before. It can be frustrating on one hand when you accidentally bite off more than you had in mind, but it's also part of what makes software development so much fun: tearing apart some giant abstract machine, refining the individual parts, and putting it back together again.

The only trade-off they made which I would have been very frustrated with had I been involved was the step away from the scripting subsystem: finding some other way of improving that performance would have meant that every change made here could be back-ported into the main engine, for the benefit of all future projects using it.

Instead now, all future "Build" console ports will be stuck with this "convert all scripts to compileable code", which makes maintenance across PC and consoles a hassle, since changes need to be made plus debugged in two places. It truly was the "nuclear" approach, which I'm sure they avoided until it became absolutely necessary. Hopefully they have good unit tests for both cases.

If the other changes do get back-ported, maybe some other project can get the console multi-core rendering working-- then those gains can be used to switch the console versions back to the scripting engine?