#it leads to better names anyway
opaque eagle
considering its been master and slave since the dawn of the computer
how could anything else be better
better for your sensibilities
ofcourse
how could I miss that
dusky pelican
Yes, because it's so clear that "master" and "slave" meant nothing more than bus timing on IDE drives. How else could you understand the roles of the drives
opaque eagle
you're the type of people to move into a new neighborhood and change street names because of reasons
the new names are more inclusive ahhhhhh
jade herald
considering its been master and slave since the dawn of the computer
we used to stuff lead into paint. just because it used to be done that way doesn't always make it better.
opaque eagle
what?
rain hawk
I mean I might change the street name if I invented and owned the street.... You know, just like epics changing the guidelines for the code they own?
Not that hard to understand
opaque eagle
its hard for you to understand how pointless it is
you're so dense and out of touch
its a waste of time
rain hawk
At the risk of sounding ad hominem, the person getting so riled up about an optional change of terms for clarity's sake is the one out of touch
opaque eagle
its not for clarity
wtf is wrong with you people
its because of
THE MESSAGE
its becasue they don'
want to offend people
who are easily offended and soft
those people
wow you're all so out of touch and unable to read as it clearly states that
pathetic
rain hawk
What message? You have yet to clarify?
The message of using terms that make more sense, aren't rooted in awkward language, and clarify usage?
It's really not that deep.
It's also optional and affects you in precisely 0 ways
How dare people respect people
Disgusting
jade herald
want to offend people
and if you prefer offending people you are more than free to continue naming things however the fuck you want... you're only required to use it if you are providing code directly to epic, or selling it to epics customers on the UE marketplace
rain hawk
Which you know, it's normal to use the guidelines of the codebase committing to
If it was a change regarding using camelCase instead of PascalCase, there would be no issues, it's just because it's removing some archaic language in favour of what they feel are more sensible terms
hybrid bloom
THE MESSAGE
what message? is this something cryptic to you?
rain hawk
As Boris pointed out, things like Master/Slave drives are just dumb. Versus something that might make things a little more clear, and less harsh.
Or an allow list, that might be a little more clear to non native speakers than a whitelist, that on its own makes no objective sense to it's purpose
The same guidelines reccomend not using slang, how is this to avoid offending people? It's just promoting good clarity and understanding across different regions
I mean it's fine to disagree, but it's not the end of the world you're making it out to be.
If you disagree, just don't use it. Most people don't use epic guidelines anyway because they have some really stupid things like PascalCase everything. This affects you in literally no way at all. It's no different to any other redesign of a coding standards. It's not taking away valuable bugfixers, it's not like they've said "sorry bug fix team, you're now the variable renaming team, guess we won't fix any more bugs. Same for you features team"
opaque eagle
as a Native Canadian who's people and relatives lie in mass graves
I don't get offended by slave, master, or Native
AS I understand words can have many meaning as im a well adjusted mature human that is a realist
not a cry baby who wants others to feel bad about silly things just to virtue signal
explain to me more white Americans how as a Native I should be offended by the use of Native in this game engine
they are still finding mass graves of my people
that is a real issue
not the use of Native in a fucking games engine
rain hawk
explain to me more white Americans how as a Native I should be offended by the u...
Literally no one has said that. In fact Epic still use it, and just say to be considerate of it use case.
At the end of the day, sure there's a million more, more pressing issues in the world. But this is a net positive change. If you disagree you get to harmlessly ignore it and it never affects you. If you did agree that some of the language makes you uncomfortable it's being addressed, and overall it's just encouraging better names for things, that are clearer, such as not using colloquialisms in your code, that may not be understood by everyone.
Epic have never professed that this is solving the world's problems, or that this is some issue, or that everyone should disavow such things, and that you should feel affected by them. They've just identified something they want to change in their code, so are doing so. It's as simple as that. Just like any other amendment to coding guidelines. If they wanted to change the case of something, or add a new object type, or change how they view const correctness, it's exactly the same process. That's it.
opaque eagle
its virtue signaling
end of story
you all love to speak for those of us who have been affected by real world issues
look at us we care
we change words to show we care
rolls eyes
rain hawk
Not at all what I'm saying.
opaque eagle
its what's happening
nocturne vector
Time to move on
Been going on for far too long
and it's clear it won't end in agreement
rain hawk
Yeah just gonna have to agree to disagree on this one
nocturne vector
Sure, it doesn't
There is also no point in endlessly going back and forth, arguing over the internet won't solve anything
Lets move on now