AnyOldName3

If it works like real WoW64, then 16 bit applications won’t work ever but 32 bit applications that don’t work will be because of fixable bugs.

AGPL is a full-on FOSS licence with strong copyleft requirements, not a measly open-source licence like Apache, which could be pivoted to proprietary at a moment’s notice. We’re communicating through an AGPL-licensed system right now as it’s what Lemmy’s licensed as. If they were going for a corporate-friendly licence, AGPL is the last thing they’d choose as it forces you to share source code with even more people than the regular GPL does.

Wikipedia management shouldn’t be under that pressure. There’s no profit motive to enshittify or replace human contributions. They’re funded by donations from users, so their top priority should be giving users what they want, not attracting bubble-chasing venture capital.

Unfortunately, I’m not the right kind of software engineer to answer in more detail than that.

I think for something like this, you’d rent cloud servers as you’d expect the number of concurrent users to change over time and ideally would be able to spin up more capacity when you need it without having to have those machines available all the time. You still need some kind of system that decides when to order more capacity with enough warning that it’s actually available (you can tell AWS you want a VM immediately, but it still takes a couple of minutes to transfer your data onto it and boot it up, which is longer than people want to sit in a loading screen) and decides which servers to assign to which users.

There’s a strong argument that the server architecture needed to be better at launch, but then the game sold more than an order of magnitude better than it was expected to, so no one would have noticed that it scaled badly had the player count been in line with their design and testing.