I don’t care for fresh (whatever it is) either, yet here we are.

You don’t need to mod the easy ones, tho

That’s a hardcore throw into the hobby, e3v1 is one of the least easy to start ones.

navalny

m*scovian imperialist, nothing wrong with m*scovites killing each other.

wah-wah it’s super hard not being slaves

tough, I don’t care about their history, for me it doesn’t exist like ours doesn’t exist for them, they’ve chosen their own path and walked it from the start of this century. My people died and die right now first to overthrow m*scovian “president” (and I for a change wasn’t behind keyboard at the time) and now to kill invaders (and I’m directly responsible that they can do it good enough given our constraints, at least in my own small unit 🙃). They could have overthrown their own creature and they choose not to because it could have ended with jail, tough.

It wasn’t

They could have tried to do something with their own cuntry, dunno something that involves less paper airplanes and going out with white flowers and more removing their leadership (but ofc they didn’t because they are the same m*scovians and actually supported their imperial ambitions before its their turn going into meatcube).

Gzdoom is an advanced modder friendly continuation of zdoom.

So no full list, just cropped screenshots? Why?

Can you uninstall it permanently?

No list, advert for proton.

Nooo, you see chosing utilitarian position is a sin.

Oh wow xlibre was shit from the very beginning who could have predicted this? Super unexpected!

Reading the linked forum thread is a gift, so many crazy peope at the same place that accuse each other being DEI hires and lefties, but this is a gem:

You guys have no idea what a mess Xorg’s source code is. I only made very small changes, but I had to spent HOURS on verifying each small thing, because changing only one line of code will cause some entirely unrelated part of the code to completely break in ways that you cannot even imagine.
You cannot even properly debug a lot of the time because you don’t know which parts of the code use which functions. The code is a giant function pointer soup that is passed around everywhere and nobody knows which parts of the code use which functions as a consequence.
…

So exactly the reason why wayland happened.

If they do it, they do it, if they don’t they don’t. Like it probably the best ending of war for us considering our elites are cumming at the thought of handling r*ssia everything. Would be bad for baltics.

That’s right.

Miraculously, once the corporate-backed enterprise maintainers were publicly put on blast, someone on the team finally decided to take a look and start addressing it. It turns out the issue was actionable all along—it just required six years of community pain, a dedicated independent researcher doing the maintainers’ profiling for them, and a front-page roasting on Hacker News to make the enterprise overlords care

Nobody ‘on the team did it’ it’s just someones personal repo. 700 mb of writes in a day and ‘destroying SSDs’ is a big overdramatization.

It’s shades of gray honestly. Sometimes they are very good (especially if you need some small tool that scratches a particular itch or want something that is 50% there right now), other times they’re extremely dumb and write horrible code. Especially of you want them to use some modern feature of your language that they don’t know anything about, or when the language in question isn’t very popular, or when the library you are using at the same time isn’t very popular, changed a lot recently and is big. They can go in circles for hours with 'wait actually …, actually …, but wait …, but actually …, ad nauseam. But when you limit them in scope, give realistic goals and constraints they more often than not work good.

deleted by creator

Or, hear me out, it could be one of the most shady companies in world (google), that has both control over infra and motive to do it.

yes, all of it

/thread

Escalate, what are you talking about?