2 ms·
>game development is still mostly happening against proprietary monoliths. Running as a monolith is the most performant way and utilizes hardware to its fulles
by DeathArrow 5y ago
>game development is still mostly happening against proprietary monoliths.
Running as a monolith is the most performant way and utilizes hardware to its fullest, which is what you want to do when you run games.
Users don't have farms of Pcs and consoles, they don't need to scale.
- skohan 5y agoWhat about a monolith ensures better performance optimization? And won't general-purpose engines pay a penalty relative to single-purpose engines since they have to optimize for the "average case" game rather than exactly one target?
- Mikeb85 5y ago> And won't general-purpose engines pay a penalty relative to single-purpose engines since they have to optimize for the "average case" game rather than exactly one target? Theoretically, yes. However so many man hours have been put into optimizing engines like Unreal that in reality the answer is no.
- skohan 5y agoI don't agree with this. I mean, UE renderer is the subject of countless hours of effort and optimization. But for instance the startup time (or build time for that matter) of a UE game is quite long and it is fairly easy to beat in a bespoke engine. That's one of the reasons looser coupling would be great. I would love to be able to use the UE renderer in the context of a different engine.