...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.
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.
The article is kind of misleading, but it's actually reasonable to take offense to Epic's coding guidelines here.
Even if it's "only" Epic Games' internal coding standard, the reality is that when big companies adopt certain coding practices is that they filter down to others in the industry. Big corps like Microsoft & Google are effectively arms of the govt so I want it to be illegal for them to even promote this shit.
Epic isn't quite that big, but since they essentially set the standard across all Unreal Engine titles, it's gross. When something like this makes it into a policy document you can be sure the rot is deep. They are undoubtedly in the process of being conquested by hateful troons and antiwhite bigots who openly proclaim theiry discriminatory actions against straight White men. They would & should be investigated and punished for that. Tim Sweeney is not the Leftard type, but he's obviously not doing a good enough job at keeping his employees in line.
...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.
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.
The article is kind of misleading, but it's actually reasonable to take offense to Epic's coding guidelines here.
Even if it's "only" Epic Games' internal coding standard, the reality is that when big companies adopt certain coding practices is that they filter down to others in the industry. Big corps like Microsoft & Google are effectively arms of the govt so I want it to be illegal for them to even promote this shit.
Epic isn't quite that big, but since they essentially set the standard across all Unreal Engine titles, it's gross. When something like this makes it into a policy document you can be sure the rot is deep. They are undoubtedly in the process of being conquested by hateful troons and antiwhite bigots who openly proclaim theiry discriminatory actions against straight White men. They would & should be investigated and punished for that. Tim Sweeney is not the Leftard type, but he's obviously not doing a good enough job at keeping his employees in line.