...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.
Exactly this. It's been standard "industry policy" since ~2020, when Microsoft, Github etc. all enforced the same. Doesn't mean it has major adoption outside of corporate monoliths. Even at work such policies are ignored - largely because any sane developer is opposed to having identifiers dictated to them.
It's a virtue signal - the engine source largely conforms to it with the exception of master (with slave entirely absent). Does beg the question of why now though?
The article makes a subtle mention of it, but this stuff was already in Epic/Unreal's "Coding Standard" back in 2022, and had been posted about in a fair number of places like here iirc. So "why now" could just be a matter of influencers/sites trying to jump on a headline opportunity.
Also, I went ahead and compared the Standards from 5.0 vs 5.4. While some predictably retarded additions or tweaks were made, there wasn't anything substantially different.
Although there was this one line that I hadn't noticed back in 2022: "Following the coding standards is mandatory.". I'm not sure if that's supposed to be legally binding at all though. I'd have to analyze the hell out of the EULA and other licensing agreements to be sure.
could just be a matter of influencers/sites trying to jump on a headline opportunity
Makes sense. A misleading article to say the least.
"Following the coding standards is mandatory."
In the context it appears, I'd imagine that is for internal use and engine contribution - which is commonplace. Organisational coding standards aren't optional by default. Explicitly stating it is likely just to reduce friction, given the number of pull requests submitted.
From memory the EULA doesn't stipulate any requirements pertaining to the structure of your own code. A cursory search for relevant terms found no mention of the standards, either. I don't see how that would be practically enforceable.
...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.
Exactly this. It's been standard "industry policy" since ~2020, when Microsoft, Github etc. all enforced the same. Doesn't mean it has major adoption outside of corporate monoliths. Even at work such policies are ignored - largely because any sane developer is opposed to having identifiers dictated to them.
It's a virtue signal - the engine source largely conforms to it with the exception of master (with slave entirely absent). Does beg the question of why now though?
The article makes a subtle mention of it, but this stuff was already in Epic/Unreal's "Coding Standard" back in 2022, and had been posted about in a fair number of places like here iirc. So "why now" could just be a matter of influencers/sites trying to jump on a headline opportunity.
Also, I went ahead and compared the Standards from 5.0 vs 5.4. While some predictably retarded additions or tweaks were made, there wasn't anything substantially different.
Although there was this one line that I hadn't noticed back in 2022: "Following the coding standards is mandatory.". I'm not sure if that's supposed to be legally binding at all though. I'd have to analyze the hell out of the EULA and other licensing agreements to be sure.
Makes sense. A misleading article to say the least.
In the context it appears, I'd imagine that is for internal use and engine contribution - which is commonplace. Organisational coding standards aren't optional by default. Explicitly stating it is likely just to reduce friction, given the number of pull requests submitted.
From memory the EULA doesn't stipulate any requirements pertaining to the structure of your own code. A cursory search for relevant terms found no mention of the standards, either. I don't see how that would be practically enforceable.
Aye, that's the same conclusion I was starting to draw after I attempted a few keyword searches.