It's not about evading responsibilty so much though as helping you decide which course of action to take when confronted with someone being ignorant.Darken12 said:The problem with "I don't intend to be malicious" is that it's a scapegoat to keep on performing the same offensive/ignorant actions and evade the responsibility of making restitutions or even owning up to what they did.lacktheknack said:That's a hell of a difference that you refuse to acknowledge.
But hey, I doubt I can change your mind. Just know that, while there definitely is malice, it's not as common as you seem to think.
Because while you have seen malice, I have also seen (and performed) incredibly offensive actions that weren't remotely intended to be so.
That's cool, we don't have to think the same.lacktheknack said:And no, I still don't think that Nintendo, of all companies, is malicious.
I understand that. I understand everything you say. I merely resent being told how I should feel (or how forgiving I should be). I want to be angry at this. Let me be angry at this. Thank you.Raine_sage said:Sorry for rambling but I just think a little empathy and an understanding that people fuck up sometimes without meaning too goes a long way towards fostering understanding between groups.
Do...Darken12 said:I literally hate Hanlon's Razor with the stabbing fury of a thousand slashers. No. It's not all innocent stupidity. There is malice in the world, and I know because I have seen it. I refuse to accept "oopsie daisy, we're all just harmless bumbling fools, tee hee!" as a valid excuse. No. At the end of the day, I do not care if it's stupidity or malice. It makes absolutely no difference to me, and I heavily resent the implication that I'm supposed to excuse or forgive or change how I feel because someone did something I highly disapprove of out of stupidity instead of malice.lacktheknack said:Again, that could take days, depending on how messy the code is (and believe me, code can get unbelievably messy).
Also, I think you're being paranoid. Never attribute to malice what can adequately be explained by stupidity, and this is definitely a case where they could have simply not thought of what their actions were implying.
The Reddit argument.Darken12 said:The problem with "I don't intend to be malicious" is that it's a scapegoat to keep on performing the same offensive/ignorant actions and evade the responsibility of making restitutions or even owning up to what they did.
And yet my viewpoints are my prerogative. We are all constantly making assumptions and decisions based on available evidence. We all have our systems for doing so. I haven't criticised yours (you can believe in the goodwill of Nintendo and the rest of the world as much as you want), so kindly refrain from doing the same with me.theultimateend said:*snip*
I don't care if it's Nintendo. I would be expressing my distaste of any company who pulled something like this. I am not buying the "we're just patching a bug!" excuse. If you want to fix a bug, you fix the bug.j-e-f-f-e-r-s said:But why? Nintendo are patching a bug that comes with game-breaking issues, as well as allowing male characters to get pregnant.
If this was a Bethesda game, we'd be calling on them to patch it ASAP. Now that it's Nintendo, why are you trying to turn it into this huge thing?
Likely there's either a "preg" piece that gets attached to existing models or a standard deformation applied to the model to apply "preg." IOW, there's like not special mpreg models.Darken12 said:I find it hard to believe that people who wanted to avoid showing mpreg in a game went out of their way to depict mpreg in the in-game models.Schadrach said:Except that the "mother" actually gets depicted as pregnant. So, it's not changing one line of dialog, it's also figuring out some reasoning behind why whenever a gay couple decides to adopt, one of them gets really fat for a while. =pDarken12 said:I am pretty sure that changing one line of dialogue from "we're pregnant!" to "we're adopting!" would have been a lot simpler than preventing the marriages altogether. They can't even claim simplicity or laziness on this one, because the lazy option was, coincidentally, the most progressive.
Not to mention that if that was the bug they wanted to correct, that should have been the bug they corrected.
But they fixed a bug, that's why we're having this conversation in the first place.Darken12 said:I don't care if it's Nintendo. I would be expressing my distaste of any company who pulled something like this. I am not buying the "we're just patching a bug!" excuse. If you want to fix a bug, you fix the bug.theultimateend said:*snip*
Yeah, evil Nintendo doing it's job. What an awful collection of bigots that Nintendo.Earthfield said:Sometimes, we forgot we're past the first decade of the XXI century...
As I have repeatedly stated in this thread, I genuinely do not care if Nintendo did it on purpose or if they're just incompetent and unaware of how shitty their bug-fixing method is. The outcome is the same either way.Sticky said:*snip*
Regardless of whether it's harder or easier to do this or that, the outcome is the same.Schadrach said:*snip*
On the contrary, their bug-fixing method is actually extremely efficient because the bug doesn't exist anymore.Darken12 said:As I have repeatedly stated in this thread, I genuinely do not care if Nintendo did it on purpose or if they're just incompetent and unaware of how shitty their bug-fixing method is. The outcome is the same either way.Sticky said:*snip*
This is why I don't like threads that devolve into programmers vs non-programmers. Easier is by definition better as a decision for the person who made this change.Darken12 said:Regardless of whether it's harder or easier to do this or that, the outcome is the same.
Right, right. Because if we take, say, WoW, and they receive a bug report about a certain ledge in an area which a player can jump from in order to bypass invisible walls, the perfect bug-fixing method is to make the entire area unavailable! Of course! Now that's some sound, intelligent bug-fixing.Sticky said:On the contrary, their bug-fixing method is actually extremely efficient because the bug doesn't exist anymore.
That's the one little factoid you seem to be missing.
He fixed the bug by removing something that mirrors real-world bigotry, thereby (inadvertently, if we're feeling generous) mirroring real-world bigotry. This is like having a faulty polygon in one of the darker skin tones and saying that the way to fix it is to prevent players from creating darker-skin characters. Or having a glitch when female models enter a certain area, so the bug fixing is to prevent female players from entering that area. Or from leaving the kitchen.Sticky said:This is why I don't like threads that devolve into programmers vs non-programmers. Easier is by definition better as a decision for the person who made this change.
One of the reasons I'm so bitterly against outrage against programmers is because at the end of the day, they're just doing their job. It was this persons job to fix a bug, and he did it.
Once again, proving why I don't like having these programmer vs non-programmer arguments.Darken12 said:Right, right. Because if we take, say, WoW, and they receive a bug report about a certain ledge in an area which a player can jump from in order to bypass invisible walls, the perfect bug-fixing method is to make the entire area unavailable! Of course! Now that's some sound, intelligent bug-fixing.Sticky said:On the contrary, their bug-fixing method is actually extremely efficient because the bug doesn't exist anymore.
That's the one little factoid you seem to be missing.
You know what method has 100% efficiency in solving every single bug ever? Shutting down the entire game so that nobody can play it.
Do you really not see the huge logical gap in your argument? Let me magnify it a bit for youDarken12 said:He fixed the bug by removing something that mirrors real-world bigotry, thereby (inadvertently, if we're feeling generous) mirroring real-world bigotry. This is like having a faulty polygon in one of the darker skin tones and saying that the way to fix it is to prevent players from creating darker-skin characters. Or having a glitch when female models enter a certain area, so the bug fixing is to prevent female players from entering that area. Or from leaving the kitchen.
It's not good bug-fixing, and I have no sympathy for whoever did this.
The politics of it are irrelevant. That's up to the company to decide. The team in charge of maintaining the game only handles logical values.Darken12 said:He fixed the bug ...
It's not good bug-fixing
I see sarcasm is lost in you.Sticky said:A far cry from what you think they have done, which is completely destroy the game and any value it may have because they made a business decision that you don't agree with. Really I think you're just too emotionally invested in this particular argument.
The politics are literally the only thing that is relevant about all this, at least to me. I could not care less about the whys and hows of this. The only thing I care about is the fact that this sloppy, lazy "bug-fixing" has ended up mirroring (and, in an indirect way, supporting) real-life bigotry.Sticky said:The politics of it are irrelevant.
Thank god there's no real programmers that think like you do. Segmentation faults and stack collisions everywhere.Darken12 said:Stopping a player from accessing a bug is not good bug-fixing, much less when doing so mirrors real-life bigotry.
When you program anything your care is in function. Everything else comes second. Everything else HAS to come second because computers aren't programmed using the powers of good feelings and positive inclusiveness. They're programmed by hard, logical facts about how that program should and shouldn't function. When someone makes a logical oversight, that can cause problems in a world that is based on 100% logical facts existing.Darken12 said:The politics are literally the only thing that is relevant about all this, at least to me. I could not care less about the whys and hows of this. The only thing I care about is the fact that this sloppy, lazy "bug-fixing" has ended up mirroring (and, in an indirect way, supporting) real-life bigotry.
False dichotomy. Implies there is no possibility of fixing a bug without that kind of undesirable results. There is. Don't paint the programmers as tragic victims who had no other choice but to do this. There were other ways of accomplishing their goals. They just did not care.Sticky said:Want that to happen? Petition Nintendo. Don't blame a mere coder and/or QA person whose mere job is to fix logical problems with how the game is currently defined.
Only if you've never programmed a day in your life. If you are working as part of a team, you have only two choices: Fix it or get out.Darken12 said:False dichotomy.Sticky said:Want that to happen? Petition Nintendo. Don't blame a mere coder and/or QA person whose mere job is to fix logical problems with how the game is currently defined.
Oh they had another choice:Darken12 said:Implies there is no possibility of fixing a bug without that kind of undesirable results. There is. Don't paint the programmers as tragic victims who had no other choice but to do this. There were other ways of accomplishing their goals. They just did not care.
Nope. They could have taken the trouble to resolve the male-pregnancy issue without banning same-sex marriage. That was an option too.Sticky said:Oh they had another choice:
They could lose their jobs.
Yeah, maybe I don't know for 100% fact how this particular instance went down. But I do know how large programming teams work, and I know how game companies typically function. And you very clearly do not. I would go as far as to say that you've never had to work with another large group of people in a company organization before based purely on how you say they should have solved this problem.Darken12 said:Nope. They could have taken the trouble to resolve the male-pregnancy issue without banning same-sex marriage. That was an option too.Sticky said:Oh they had another choice:
They could lose their jobs.
Let's get one thing straight: unless you work for Nintendo and were there when they were handling this bug, everything you're saying is purely hypothetical.
Then you care more about feeling good than actual truth or facts. The devil is always in the details, and you so casually saying "ALL I'M SAYING IS THAT THE PROGRAMMERS AT NINTENDO ARE WRONG" completely misses why they did that, what the correct approach is, and how in the future this could be addressed.Darken12 said:And as I have repeatedly stated, I care far more about the outcome than the intricacies
That's not what I'm doing. I am expressing my opinion in an open forum. You are the one repeatedly challenging my opinion and using hypotheticals to try and sway me. I have repeatedly stated that I do not care how or why it happened. I do not care if it was a programmer who did it wilfully, or because he didn't know better, or because it's a tyrannical workplace environment. I do not care if it was a direct order from the higher-ups and the programmers were doing what they were told. I do not care about the programmers and I am not blaming them for anything. My anger is directed at Nintendo as a company for the end result that we are currently witnessing.Sticky said:Turning everything into a bad guy / good guy scenario only paints you as being extremely emotionally charged.