These revenge forks never live long.
This one didn‘t even manage to delete Godot from the readme and insert its own name.
This one didn‘t even manage to delete Godot from the readme and insert its own name.
Several contributors cannot work on Godot anymore, hence the fork.
So that doesn't really seem to be the reason why that fork was created. Maybe it's someone who was unhappy with the development in general and this was the reason to pull the trigger but overall this does look a bit off.
But apparently the redot discord server is buzzing and this already has 1500 stars. More than I'd expect for a pure revenge server. Who knows what's going on at this point?
Seems about right to me. Don't underestimate how organized and developed the anti-woke outrage machine is, and the fact that this blew up on Twitter when the "game engines are woke" meme was ascendant. It's a perfect tempest in a teacup.
I mean, it's literally just a fork of Godot with a reskin at this point, that few people would even know about outside of the context of the controversy that led to it. What reason would is have for having as many stars other than hype and virtue signaling political alignment?
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.
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.
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.
No, we won't be making games together. We are not in this together. We will never be.
Redot and similar acts of standing up are proof of life. You will not stamp out life.
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.
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.
Assume a talented programmer who wishes to involve another programmer to help work on their (unaccepted by upstream and therefore mostly invisible) changes - github is then used to facilitate the work easier than setting up your own private repo. He can then approve that 3rd persons changes and move on to the next thing.
The key to it is they control the choice to accept the pull request and "make it so".
Years later, the potentially stalled upstream can "backport" the best changes from the fork if they have diverged too much to merge all of (the fork) changes into (to the main original) repo, and there is some reason to keep the stalled code alive (not saying it's stalled), or if it is still or more active probably "sideport" would be a better word, and if more advanced the best parts from Redot could be collected as a "patch" especially if it is not clear which is the most active. If Redot becomes the de factor dev version, and merging is too difficult, the original maintainer could ditch the old repo putting up a message and link to Godot non-Faggot version, fork Redot back into Godot, call it the release version, and call Redot the live public beta of the next version of Godot (this is my prediction of what will happen).
Jacob Faggot was a Swedish scientist, civil servant, and surveyor. * this is a test of the anti-woke emergency broadcast system. Pump up the volume.
The reason Juan has given for blocking were github comments that were such that he had to block them. I haven't seen them so I can't verify it but the fact that it was limited to very few accounts compared to what happened on social media leads me to believe that argument.
Don't get me wrong, Godot did ban few accounts. Those totally weird hecklers who made issues and PR's trolling against basic human rights.
Again, if you have a proof of a ban campaign of ACTUAL contributors, please show it.
Or is your claim that one day, for no specific reason, they just started banning random people?
No point panicking about replacing references. There's so many in the engine, like there would be in any codebase anyway, that probably most of them will stay as-is. I don't imagine there was any project-wide Ctrl+H on Open/LibreOffice port either.