...That's not entirely accurate. I'm fairly certain the coding "standards" only apply to those working on the engine itself at Epic. And there's no fathomable way they could try to apply and force this metric on outside studios.
Still supremely lame clownworld nonsense, but not quite as bad as the headline tries to indicate. The worst part is probably the amount of wasted time and bugs it'll produce, that could've been better spent internally on improving the engine.
A lot of game studios use Unreal Engine's guidelines for themselves for several reasons. The main reason I think is that when a game developer with expertise in Unreal onboards to a studio that uses the engine, it makes the transition much smoother (Imagine going from studio to studio working on games using the same engine but writing code under different guidelines each time). Another reason is that the existing guidelines saves studios a lot of time writing their own from scratch.
Oh I'm aware of that. But a small studio that's more focused on getting the job done and creating games isn't going to give a rat's ass about following those DEI sections, not unless they're already gunning for DEI handouts and/or full of a woke development team in the first place.
The actual technically significant parts of the standards obviously would be useful to keep on hand for anyone writing any code, and most of the DEI stuff is comprised in one subsection, so it'd be easy to just skip that stuff for what it is: meaningless fluff.
...That's not entirely accurate. I'm fairly certain the coding "standards" only apply to those working on the engine itself at Epic. And there's no fathomable way they could try to apply and force this metric on outside studios.
Still supremely lame clownworld nonsense, but not quite as bad as the headline tries to indicate. The worst part is probably the amount of wasted time and bugs it'll produce, that could've been better spent internally on improving the engine.
A lot of game studios use Unreal Engine's guidelines for themselves for several reasons. The main reason I think is that when a game developer with expertise in Unreal onboards to a studio that uses the engine, it makes the transition much smoother (Imagine going from studio to studio working on games using the same engine but writing code under different guidelines each time). Another reason is that the existing guidelines saves studios a lot of time writing their own from scratch.
Oh I'm aware of that. But a small studio that's more focused on getting the job done and creating games isn't going to give a rat's ass about following those DEI sections, not unless they're already gunning for DEI handouts and/or full of a woke development team in the first place.
The actual technically significant parts of the standards obviously would be useful to keep on hand for anyone writing any code, and most of the DEI stuff is comprised in one subsection, so it'd be easy to just skip that stuff for what it is: meaningless fluff.