imownbey

For cost we put repositories into cold storage once they are not read for a week. This helps long term costs stay pretty minimal. You can also delete repositories via the API if you’d prefer.

Two things you are missing is:

1. With NFTs games can take a cut of resales. With something like cs:go there was a substantial secondary resale market for things like skins, which valve wasn’t able to capture but with NFTs they could have taken say 10% of each resale.

2. Because the data is public it’s possible for other games to bootstrap off the data (we have seen this with “airdrops” in the crypto land). Meaning a game which is coming out can give some perk to people who own X in fortnite because they think their game is similar and want to entice people to try their game, especially people who they know like fortnite.

In the tech world we are always talking about how valuable data is. The blockchain makes that data public so secondary products can exist to serve needs the game doesn’t care about. And provides the ability for the original game to capture part of that market if they wish because they own the initial contract. But because the data is public, other games can also use that data how they want.

"Calvin's primary trade-off is that it doesn't support session transactions, so it's not well suited for SQL. Instead, transactions must be submitted atomically. Session transactions in SQL were designed for analytics, specifically human beings sitting at a workstation. They are pure overhead in a high-throughput operational context."

Is this specifically for distributed SQL only? I think there are some scalable SQL systems that don't support sessions either.

Woah this is super fun and nothing was wrong with it. It was kind of annoying but I feel like all sims are that way. I want to be able to run different airports!!!! And a mode that just goes on forever would be awesome.

Yeah in retrospect we should have definitely done this. Although it causes a significant trade off to prototyping speed. I am not sure if its not just worth using your own API at that point.

So I would recommend using Parse after the end of the year once they figure out their reliability. Infrastructure as a service that is in the process of improving reliability is not very confidence boosting, though.

But I do appreciate that yall have started posting on status.parse.com! That is a major improvement in the right direction.