I mean, hey: it worked to make Apple finally drop their proprietary charging connector. As long as the cost of losing business in the EU is higher than designing an EOL transition for games and hiring developers to actually do it, it’s in their best interests.

what I just outlined as what would have to happen.

The backend server stack hosts a set of tightly intertwined services that conform to an Application Programming Interface. You quite literally do not need to provide the entire stack designed for multi-hundred-thousand concurrent players just to satisfy that interface the game clients are expecting. It costs time and money, but they could damn well just create an implementation designed for simpler, small-scale hosting.

Oh yeah, just do that, as if that’s a super duper easy task to do.

If you designed it for that eventuality, yeah, it’s easy to do. Trying to retrofit that into an existing system designed solely to run at cloud scale is a bloody nightmare, and that’s not at all what SKG is asking for.

because “direct connection” means no concept of an account anymore, and if everything is tied to your account, the whole damn game doesn’t work now.

Counterexample: private World of Warcraft servers. They implemented their own, and it’s worked fine for them.

The account system is just another API. The client uses it to authenticate, and the dedicated server uses it to verify the client authentication. Fuck, even Minecraft and it’s poorly-designed multiplayer can do that. As long as the client and server use the same auth provider, you can still have “accounts” without relying on Mojang’s insanely censorship-happy official login system.

It’s possible, sure, but by this point you’ve effectively remade a very large amount of the game from scratch so who cares now.

I’ve made this exact same argument you’re giving here, and yeah, I know it’s not easy. I sympathize with indie developers who are over-designing their server architecture and might not have the resources to do this, but a AAA game studio can afford to hire more developers for their next game instead of C-suite bonuses.

what if parts of that executable have still in use proprietary pieces that are used in other games they own?

I also made this argument before, and it is valid criticism. It’s worth pointing out that the valuable and reusable proprietary parts are the infrastructure and design, not the game logic.

I’m not an entitled twat. I understand that there are legal challenges and big, open-ended questions on how developers could actually pull this off. Making large, consumer-exploitative developers like Epic, Bungie, or Blizzard have to hire more developers isn’t a good enough reason to make me discount an entire consumer-rights movement.

As long as the kernel keeps supporting loading and executing processes with 32-bit code, they don’t even need to go that far. There shouldn’t be much stopping Valve from just supplying libraries themselves inside a container. In fact, that’s what the Steam Linux Runtime “Sniper” does.

People with planet-sized egos really need to stick to DPS roles.

Modern game servers for major games are simply just not designed to be run locally bare metal. They’re often in the form of complex stacks of multiple moving parts, shit like entire k8s deployment stacks with like 12 distinct resources, many of which might be tightly coupled to implementation details.

They wouldn’t need to release the whole stack to satisfy the requirements. Release the dedicated server executable and patch the game to allow direct connections to servers.

For an MMO it would be more complicated, but the movement also isn’t asking to be applied retroactively. Existing MMOs built for scale are free to keep their current architecture. The only requirement would be that future MMOs are designed with an EOL transition plan.

They release, say, v2.4 of their game server program in 2025, it’s tightly coupled to the auth server v1.7 api.

It’s an API. Unless they hardcode the IP address it or use certificate pinning, it can just be reimplemented.

[Citation Needed]

It’s not like they needed all 11000 of them. Half of them died from being submerged in boiling dye… Surely, it would have been easier with half a magnitude smaller quantity.

https://amiunique.org/fingerprint

std::string doesn’t have a template type for the allocator. You are stuck using the verbose basic_string type if you need a special allocator.

But, of course, nobody sane would write that by hand every time. They would use a typedef, like how std::string is just a typedef for std::basic_string<char, std::char_traits<char>, std::allocator<char>>. Regardless, the C++ standard library is insanely verbose when you start dropping down into template types and using features at an intermediate level. SFINAE in older versions of C++ was mindfuck on the best of days, for example.

Don’t get me wrong, though. I’m not saying Rust is much better. Its saving grace is its type inference in let expressions. Without it, chaining functional operations on iterators would be an unfathomable hellscape of Collect<Skip<Map<vec::Iter<Item = &'a str>>>>

TypeScript […] only adds syntax, and doesn’t re-write it.

I believe enum, const enum, and decorators would like to have a word with you.

Swift also uses backticks and Rust has a dumb one in the form of r#thekeyword. Still much better than introducing a async as a new keyword in a minor version of a language and breaking a bunch of libraries.

Rust is verbose, but C++ might still take the cake with its standard library templates. Especially when using fully-qualified type names…

auto a = ::std::make_shared<::std::basic_string<char, ::std::char_traits<char>, MyAllocator<char>>>();

A reference-counted shared pointer to a string of unspecified character encoding and using a non-default memory allocator.

What’s next, leaded gas?

Actually, probably. It’s a good way to make people grow up dumber and more irrational, and that’s basically the target demographic of their party.

This means either them or more junior developers will be brought in as glorified prompt engineers.

Oh, sweet summer child. It’s not going to be junior developers; they still have self-worth. An un(der)paid intern or outsourced contractors, however? They’re fine working for scraps and no health insurance.

It’s a small comfort that even Twitter is giving this take the reception it deserves.

It’s kind of wholesome. People coming together to tell the guy who built a child-exploiting, underaged-gambling “game” for kids to get fucked brings a tear to my eye.

Founding Roblox isn’t exactly building the interstate highway system, creating antibiotics, or inventing the telephone, John.

And look where it’s gotten us. Drunk on arrogance and the suffering of millions

You made Roblox in order to monetize children’s naivety. We’re not giving you the nuclear codes for shit

Because you’re a bunch of sociopaths with a Messiah complex

You build a giant ad platform and called it innovation. You’re modern day carnival barkers. Go fuck yourself

And unregulated gambling. Can’t forget the whole item market aspect, where goods trade for higher and lower value based on speculation and demand like real-world securities do.

It wouldn’t even want them. Watch as it regrets its mistake and chucks them back up as Hawking radiation.

He thinks he’s hurting blue states, but he’s mostly going to screw his voters.

There’s a 0% chance he gives the money currently earmarked for FEMA back to the individual states or redistributes it in a way that lower-risk states are paying more towards higher-risk states. The leopards are going to be well-fed from this stupidity, that’s for sure.

I think we should be subsidizing people’s poor reading comprehension.

Why should the poor subsidize their income with our labor?

the poor … our = us
their = the rich

This commenter was asking for someone to try and justify why we (the working class) should have our labor contribute to the income of people whose existence is based on exploiting others. A perfectly reasonable question.

One instance? There’s at least two. But does that really matter? Reddit had r/TheDonald and r/conservative, and trying to get those people to fuck off and stop proselytizing elsewhere was like trying to play whack-a-mole against an anthill.

Here, you block the tankie instances and move on with your life.