The thing about IT for older folks is you have to be up for conversation too. Most of the customers I have only get out for church, so if I come out to see them it might be the first conversation they’ve had in days.

Inefficient/unoptimized would be an accurate description. I think it’s important to add, for bethsoft games specifically, that the save includes all changes to objects, even if the player themselves didn’t interact with them(e.g. Physics interactions, explosions moving things, npcs bumping stuff around), and also includes all NPC changes. Master files(ESMs) get loaded, then the save loads the changes it has baked in to the databases. So, when you load up a save that has traveled the world and loaded a lot of things into save memory, the engine has to sit there and reconcile all the changes with the ESMs, which can add up quick if you’re playing modded.

Save bloat is more often related to excess values not being properly discarded by the engine, if I remember right. So it’s not that the objects themselves take up a lot of space, but the leftover data gets baked into the save and can end up multiplying if the same scripts/references/functions get called frequently.

It was a lot worse with Skyrim’s original engine, and got better in Fallout 4 and Skyrim SE. The worst bloat happens with heavy modlists, of course, as they’re most likely to have poor data management in some mod.

It is also wholly possible that Steam changed the availability themselves, so you can’t take all the blame away from them, but like I said originally, this is Sony’s fault first and foremost as the publisher would have first say on regional availability.

There’s no way Steam is 100% in charge of what regions a game is available in. The publisher absolutely has a say in where, and if it was available in all regions at the start that was on purpose.