1000% this. Without giving away too much information, I work(ed) for a cloud provider (not one of the big ones, there are a surprising number of smaller ones in the field you’ve probably never heard of before). I quit this week to take a position in local government with some quaint, on-prem setup.

1. We were always understaffed for what we promised. Two guys per shift and if one of us took vacation; oops, lol. No extra coverage, just deal.
2. Everyone was super smart but we didn’t have time to work the tickets. Between crashes, outages, maintenance, and horrendous tickets that took way too much work to dig into, there was just never enough time. If you had a serious problem that took lengthy troubleshooting, good luck!
3. We over-promised on support we could provide, often taking tickets that were outside of infrastructure scope (guest OS shit, you broke your own server, what do you want me to do about it?) and working them anyway to please the customer or forwarding them directly to one of our vendors and chaining their support until they caught wise and often pushed back.
4. AI is going to ruin Support. To be clear, there will always be support and escalation engineers who have to work real problems outside the scope of AI. However without naming names, there’s a big push (it’ll be everyone before too long, mark it) for FREE tier support to only chat with AI bots. If you need to talk to a real human being, you gotta start dishing out that enterprise cash.

Mix all that together and then put the remaining pressure on the human aspect still holding things up and there’s a collapse coming. Once businesses get so big they’re no longer “obligated” to provide support, they’ll start charging you for it. This has always been a thing of course, anyone who’s worked enterprise agreements knows that. But in classic corpo values, they’re closing the gap. Pay more for support, get less in return. They’ll keep turning that dial until something breaks catastrophically, that’s capitalism baby.

Check out https://www.giuspen.net/cherrytree/, lightweight note-taking app with interesting scripting function built in.

Even if that’s not your cup of tea, it has the option to save your notebook to a single sqlite file, so I take that as good enough proof it’ll work for your similar purposes as well.

This kind of infuriates me. On rare occasions loading into the game (unmodified) it’ll glitch out and forget to render the borders for a good 5 minutes or until first teleport. Like come on! I can see it! I know you’re doing it!

Another game, Code Vein (shut up, I love it, just embrace some trash from time to time) did the same thing. I could tell because the layering was messed up and your partner’s nameplate would render over the black borders by mistake …

Disappointing, but somehow inevitable.

"This will enable us to release the vast majority of games that use it. "

So it sounds like the floodgates are opening and now it’ll be up to the users to sort out the flood of BS. None of this is truly surprising, while I’m not cynical enough to suggest their temporary stance was a quick way to score some easy points with the anti-AI crowd, we all kind of have to acknowledge that this technology is coming and Steam is too big to be left behind by it. It stands to reason.

I also understand the reasoning for splitting pre/live-generated AI content, but it’s all going to go in the same dumpster for me regardless.

I certainly think it’s possible to use pre-generated AI content in an ethical and reasonable way when you’re committed to having it reach a strong enough stylistic and artistic vision with editors and artists doing sufficient passes over it. The thing is, the people already developing in that way would continue to do so because of their own standards, they won’t be affected by this decision. The people wanting to use generative AI to pump out quick cash grabs are the ones that will latch onto it, I can’t think of any other base this really appeals to.

So it could possibly be construed to “Microsoft’s Dirty Operating System”, yeah?