Deciding how to invest my resources, where to expand, when to attack, defend, or retreat, scouting and countering my opponent’s plans…
…but when it comes to the physical act of doing this stuff, it feels so horribly awkward that it’s like I’m fighting the UI more than my opponent.
Clicking and dragging selection boxes as if my troops are always in a rectangle formation? Right-clicking to attack but accidentally moving instead… And ugh, the endless series of tedious build queues.
The actual mechanics feel more like data entry — the kind with real bad RSI — than military leadership.
Job listing for back-end engineer at Arrowhead says:
Cloud Engineering: Utilize Azure services to build and optimize cloud-based backend components and make use of monitoring tools to track live performance.
Early days playercount woes were before they added more nodes to their solution.
CEO said during the early day playercount woes:
It’s not a matter of money or buying more servers. It’s a matter of labour. We need to optimise the backend code. We are hitting some real limits.
They can’t just fire the people maintaining their solution either but that’s also baby bucks
A good back-end engineer is at least 100k. And a just-keep-the-lights-on crew is probably 3-4 of them.
FWIW: I also work in IT, on an IoT system that you might also assume has a “nonexistent” server cost. (I assure you, the cost exists.) I also used to work in game dev.
That said: Yeah, protesting by playing the game is a severely misguided notion.
Descenders. Just has a real nice flow state quality to it. Chill soundtrack. You can play as fast or slow as you want to. No pressure to do tricks or get high scores. Just making it to the finish line eventually is enough.
Copyright duration and rules are ripe for a complete overhaul, but it is worth noting that the so-called “Mickey Mouse Protection Act” really just put the US in line with the other countries in the Berne Convention, which the US had dragged its feet on signing onto for decades. Once the US agreed to respecting international rules for IP, offering a shorter copyright duration than Europe was an obvious disadvantage.
“Okay, I know you weren’t too happy about my plan to retroactively charge you for every mile you drive in the car I already sold you… What if I told you, I’ll only charge you for a maximum of… uh… 30,000 miles per year?”
Reasonable people can debate how the pricing should be structured, especially when it comes to online functionality that doesn’t even take a penny of Nintendo’s server budget…
But I don’t think it’s reasonable to expect zero cost at all, when:
Console manufacturers have an unavoidable incentive to sell hardware at a loss (even without factoring in the platforming costs+risks) and make up for it in software sales and add-on services
…and they suffer the reputation hit if any of their offerings are not up to par, in a way that e.g. Windows does not, so they have an unavoidable interest in monitoring and triaging issues with games
…and networked components tend to be the most sensitive and most traceable part of any software system
…and scaling issues tend to be a cross-cutting concern that a third-party vendor who isn’t intimately familiar with the client codebase can affordably help with
It’s just part of the deal you make when you sign up for a walled garden. You get certain guarantees, but only if you pay for the relevant package. You can’t have it both ways – getting the benefit of first-party backing while enjoying the freedom of a purely third-party environment. It’s like a cruise ship that doesn’t let you bring your own alcohol.
I did watch the response video before commenting. Did you read the forum post? He said it’s all settled, it’s just gotta go through the bean counters now. But the fact that he emailed them immediately before posting proves that he knew it was not all settled.
What if they replied “Actually, you can’t just reimburse us for that. The manufacturing process that produced it is being overhauled and we won’t be able to replace it for at least 6 months and we’ve got conferences to demo at between then and now. We need you to get it back.”
I’m glad GN didn’t reach out. Linus emailed Billet Labs 2 hours after the GN video with an offer to reimburse them for the prototype, so that he could claim that GN got their facts wrong. But we have the receipts!
That was the nail in the coffin, for me. Making mistakes is fine, even big ones. I understand that Youtube is the devil, and it’s easy to fall into a trap of shoveling nonsense out onto the platform. I’m honestly sympathetic to that. If Linus said “You’re right, quality has suffered cuz we’ve been going too fast. We need to take another look at this.” I’d be completely happy.
But to lie – not just by words, but by actions – in order to cast doubt on the people who are trying to give you a reality check and get your work back on track… That’s really bad.