I agree with your first statement, but disagree with the rest. I am not their target market. I enjoy playing their games, but primarily because I am spending time with the kids as I do. Not many of their games are targeted to my demographic.

I disagree that they focus only on digital. Every single Nintendo game comes out on a physical chip. And sales on digital copies are rare and minor (30% off maybe). It is often cheaper to get a physical copy on sale cheaper than digital. And you can then sell it / buy it second-hand. I’ve read that with Switch 2, even the digital codes can be transferred to a new owner. Nintendo for all their faults have never forced you to lock in a digital library you can never resell.

I bought it second hand. Nintendo got $0 from the sale. In fact, two thirds of our physical games have been purchased second hand.

You might be surprised. I came to the Switch party super late when I bought my kid a switch Christmas 2023. He’s all over Zelda now, has BotW, TotK and even Skyward Sword on his Switch. For him, these games are all from the last year. He turned 2 the year BotW was released.

It’ll be the same story with Switch 2. Some kid who might not even be born yet will get a Switch 2 in 8-9 years and come across these games with all his school friends.

I doubt I’ll go the Switch 2 path with the kids. I haven’t seen a reason to upgrade, yet. I’m thinking of the Steam Deck - while the Nintendo had a fairly cheap entry point to get on the platform, I’ve spent enough on games to negate the difference between a Switch and a Steam Deck - where I already have a 500+ game library to play on it.

Oh hey! That’s us!
We’ve known about this issue since March. OP’s post is a very good explanation of the problem. Lemmy wasn’t designed with one huge instance in mind like this and lemmy.world is the only instance I’m aware of being a problem. Our Kiwi sisters and brothers hacked around the problem five months ago: They set up a server in Finland, slurp up bulk lemmy.world content in batches and then insert that content into their local database. They invited us to share their code to do this, but:

1. It required us to spend money on a VM in Finland specifically for lemmy.world content - a precedent that made us hesitate.
2. This is a temporary problem, a new version of Lemmy was meant to come out some months to remedy it. It simply hasn’t been released, yet.

Had we known in May that this would still be an issue in October, we might have chosen differently.