Where is the proof these people are "racist cheerleaders?" If someone called you an anti-White, misandrist, child groomer, etc., you'd demand them to back up the claims with sources.
First, getting blocked on GitHub doesn't remove your access to the repository. You can still see and fork the code. You just can't comment in issues and discussions.
Second, no actual developer of Godot has been blocked. Random people harassing the contributors have been blocked.
No weird hecklers and no one trolled against human rights, except for the people in charge of Godot trolling against the human right to free expression of course.
Nobody threatened your very obscured sense of free expression.
They didn't ban them from the platform (even that would be discussable), they simply stopped interacting with a bunch of very weird and intolerant people.
It's their right to ignore toxic people.
Outrage machine? You mean people sincerely disagreeing with the hateful bullshit the Godot community managers and moderators have been saying publically?
It's a way to dehumanize the majority of people who'd like to keep politics out of professional game development.
There's no way to argue that this whole controversy wasn't just made up on purpose by a radical CM. At some point companies have to learn having these people in control of the social media profiles isn't a good idea, and siding with them is even worse. This is peak unprofessionalism and trying to poison the community well.
"on purpose" gives too much credit. No one ever knows when some random tweet suddenly becomes a hurricane. That's why PR tries to be as milqeutoast in posting as possible. Often never allowed to even reply to any but the most obvious questions woth the most canned responses (when is X comkng out. And not much more).
But yes, the various issues with the community (even before the Unity implosion) and its design philosophies that show no hint of changing (which are fine, just not to my needs) is why I'm looking more into Stride for my OS engine instead.
Or at least that was the plan until layoff season came. Hope 2025 gives me better stability so I can get back to my long term goals.
I see the argument in saying the CM would do that accidentally, but don't personally buy it. They are supposed to be professionals in this, yet their post implying a stance ("woke is good and relevant to game engines") of the whole Godot community is something that could only be considered "neutral" for people who insulate themselves from said large community.
Ideally I'd like the devs of projects to handle their tweets themselves, even if they tweet less, and not be overly milktoasty about it. But the standard is in the Mariana Trench given for many companies a Golden Retriever would be a better CM. I hope Godot/Redot somehow survives this with the larger community intact.
Btw, Stride is cool. As a C# game dev for 10 years, I love to see non-Unity C# engines actually being used/seriously considered!
"they" posted "Apparently Game Engines are woke now" "show us your #wokot games below", which is obviously rage bait, in response to a stupid tweet with minimum traction.
She blocked mild criticism, and then I kid you not, posted a selfie of herself in the shower, to flame Asmongold due to his video on the subject.
Saying that something is "random" is completely ignoring the fact that at every chance she had to be obnoxiously queer, she took it.
Xananax also posted a unprofessional message on the official website linked discord, and then the so called official response to the situation made excuses saying that this discord isn't official.
They've had many instances to act better, distance themselves from the unprofessional behavior and didn't take it.
How do you know what the majority wants or that even matters?
Simply because some sociopaths have stopped seeing themselves as active members of the society, doesn't necessarily make them neither a majority nor a healthy group of people.
To honor basic human rights is "poisoning"? That's some strong projection.
I think your reply unintentionally just strengthens my point. You just double down on the dehumanization and polarization while sounding like you're out of touch with the majority.
Polarization like... staying tf away from racists, homophobics, genocide supporters and in general toxic people?
Yeah, i guess that's the kinda of polarization that i can support. Majority or not.
Doubling down on irrelevant labels is just self projection from you at this point.
But in abstract, people want to make games. If you go looking for trouble and try to shed more and more layers off, eventually you're left only with radicals and yes men. The obvious choice is to just not bring politics to arenas where people are strongest just playing to their strengths together. Forcing in partisanship for no reason only makes the whole weaker in their mission, while also becoming an echo chamber.
Make games with everyone that wants to make games, for everyone that wants to play games. Or get out of the industry.
History is filled with workers of any kind standing up, speaking politics as part of their unions, taking action as one and having the black sheep marginalized.
No, we won't be making games together.
We are not in this together. We will never be.
Comparing worker movements to this is hilarious, is rhymes with the current woke agenda of making people think they are "the resistance" even though they're just being cogs of a hate machine, saying the same things corps, celebrities, and the telly is. You are free to condemn yourself to be swept away after taking part in your authoritarianist ways without having any defense after, having dehumanized your kin.
Redot and similar acts of standing up are proof of life. You will not stamp out life.
Polarization like... staying tf away from anti-White racists, misandrist, antisemetic genocide supporters, child groomers, and in general toxic people? Yeah, i guess that's the kinda of polarization that i can support. Majority or not.
"Be specific" sounds like a high-stakes interview, so I'd better answer. :)
* SITUATION: Factory reports MVP factory stations for pilot customer "not turning on" for the day, reason unknown.
* TASK: Get stations up in time for production line, so startup doesn't go out of business.
* ACTION: Determined cause was unexplained networking problem outside our control, and that was triggering some startup time checks. But that the stations were resilient enough that I could carefully edit the code on the stations to relax some timeouts, and enough packets were getting through that we might be able to operate anyway. After that worked for one station, carefully changed the remaining ones.
* RESULT: Factory stations worked for that production day, and our startup was therefore still in business. We were later advised of the submarine cable failure, and the factory acknowledged connectivity problems. Our internal post mortem discussions included why the newer boot code hadn't been installed, and revisiting backup connectivity options. From there, thanks to various early-startup engineering magic, and an exciting mix of good and bad luck, we eventually finished a year contract in a high-quality brand's factory production line successfully.
No technical wizardry in the immediate story, but a lot of various smart things we'd done proactively (including triaging what we did and didn't spend precious overextended time on), plus some luck (and of course the fact that some Internet infrastructure heroes' work had them routing any packets at all)... all came together... and got us through a freak failure of a submarine cable we'd never heard of, which could've ended our startup right there.
(Details on Action, IIRC: Assumed command of the incident, and activated Astronaut Mode manner. Attempted to remote access, and found network very poor. Alerted factory of network problem in their connectivity to AWS Singapore, but they initially thought there was no problem. Could tell there was some very spotty connectivity problems (probably including using `mtr-tiny`), so focused troubleshooting stations on that assumption. Realized how the station would behave in this situation, and that the boot-ish checks for various network connectivity were probably timing out. Or, less likely, there could be a bug in handling the exceptional situation. Investigating, very slowly due to poor Internet, found that the stations didn't have the current version of the boot code, which would've reported diagnostics better on the station display, so factory personnel might see it and tell us. Using `vi`, made careful, minimal changes to the timeouts directly on one station, in the old version of the the code on there (in either Python or Bash; I forget). Restarted station, and it worked. Carefully did the same to the other stations. Everything worked, and other parts of the station software had been done smart enough that they could cope with the production day's demands. Despite the poor connectivity, and the need to do network requests for each production item that passed through the station, before it could move on.)
