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.
> 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.
So what is EA's incentive to join the Valve blockchain where Valve gets 10% of each resale? And if there's no incentive for EA to join, why isn't it just a centralized marketplace rather than a blockchain?
> 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.
Valve and other companies already have this data, in much greater specificity than "this wallet owns a longsword".
1. I think Valve takes a cut of every marketplace sale, as well as the game publisher. More importantly they control the market completely so they surely can choose what share to take on every sale. They certainly don't need NFTs.
"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.
Calvin is a generalized consistency protocol, that we use in FaunaDB to support relational semantics (but not SQL) in our database.
Multi-query transactions can be useful, but the FaunaDB query language is functional, rather than declarative like SQL, so composing queries that can do everything you want is usually easier than SQL.
FaunaDB's query language makes it straightforward to do it the first way. All queries are serializable, so any preconditions checked would gate transaction commit as you would expect, and read-modify-write style transactions work.
Is the wire format roughly isomorphic to the structure above? Or does the Scala library convert this code-like structure into something simpler/flatter?
(BTW, would be nice if I could read your API docs without signing up for an account.)
It is isomorphic; right now it's layered onto JSON, but eventually we will support CBOR on the wire as well. Internally everything is CBOR with LZ4 block compression.
The docs will eventually be available without an account.
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.
The iPhone client was really good and really solid. Unfortunately we had to migrate off of Parse though because of pretty consistent downtime and really slow speeds. It wasn't unlikely for Parse to go down for at least minutes at a time once a day. Migrating off of it is not easy because you have to then replace the really solid client which can take some time to reproduce some of the features you have ended up relying on.
The dashboard also left a lot to be desired. It limits how many tables it shows on the left so you end up having to hack the URL. I believe they finally offered a "fullscreen" mode rather than having a fixed width and height which is nice. Basically we would have to drop down to the Ruby client to audit the data often which isn't the worst.
Parse would also just write random blank rows all the time whenever we did concurrent writes (this is a known bug https://www.parse.com/questions/duplicated-empty-objects-cre...). They have just moved over to the Facebook Developer bug tracking which is pretty awful as well.
Parse was really good to prototype on which was nice, but it is extremely likely if you want to launch anything to the app store and don't want to deal with downtime you have no control over you will need to rewrite it. For this reason I would suggest with just using something home grown.
Hey there, I work on Parse. This is good feedback.
Improving reliability is our #1 priority right now. The bulk of our team is solely focused on it. We've made some good progress and hope to have things in a much better place by the end of the year. You can follow it all on our status page. We try to be very transparent with post mortems and such.
That bug sounds nasty. I'll take a look to see if it's still an issue but I believe it was fixed a while ago.
The Facebook bugs flow has its pros and cons but I believe it's been great for our community on balance. We have an awesome team of folks triaging and repro'ing bugs and interacting with the community thanks to our integration there.
Drop me a note at ilya@parse.com if you have more thoughts about the dashboard or anything else.
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.
I just mean to say that we've prioritized it above all else and are really crunching to make it a non-issue for our developers. Our traffic has exploded in the last year so we need to rework some things.
To address the "moving off of Parse" comment: The way I've dealt with this is to use the Parse REST Client instead of the Parse SDK. That way you're object model isn't tied to parse PFObjects and you can swap out the Networking layer if you choose to move to another vendor. If you control the full stack, you can even model your backend to more-or-less mimic Parse's Rest API.
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.
That gif is quite childish – but also entirely correct. schoper is awesome at spouting cleverly disguised standard racist talking points. Nothing interesting to see there.
>think of what the racial makeup of prison would look like 5 years after you started giving smarter people lesser sentences due to their lower rates of recidivism (and vice-versa)
The above statement implies that if you let smart people out prison, the racial makeup of prisons would change. This indicates a position of assigning a pretty high correlation to intelligence and race; ie, a prejudice based on ethnicity. Seems pretty clearly racist to me.
This seems like an unfair comparison. While people buy new Porsches and Jaguars when they need them I think a lot of people have been buying Tesla because of the novelty.
This doesn't make this any less impressive, but I am not sure that it is fair to make the comparison of a company which needs to generate novelty year after year (like Jaguar and Porsche) with an entirely novel company (like Tesla).
If Tesla was putting out yearly models than this would be much more news.
>> While people buy new Porsches and Jaguars when they need them
....meeeeh, nobody really neeeeds a Porsche, they just buy them for the novelty (of sportiness) one could say. I think a Tesla in certain areas (anywhere near a big city) could make a much more practical purchase than a Porsche...
edit: Also, 60k ain't what it used to be. Heck, you'll pay that for a 3-series BMW these days (335i).
Although this is true, I think it is missing the point. What was the problem text messages was trying to solve?
A quick, semi-personal connection between two people across a distance. This can further be boiled down as humans interest in connection and conversation.
It turns out that Twitter, due to the social network (both existing and being one sided) solves this problem better then text messaging. So really it evolved text messaging.
This is much like the quote by Henry Ford "If I had asked people what they wanted, they would have said faster horses." Ford was not "solving a real problem" -- the problem of transportation had already been solved since the dawn of time. He was evolving the solution to a faster, more convenient method.
As an entrepreneur on the look for the most fertile soil, evolving an existing solution has the highest potential pay off. Plus the thought of frankensteining multiple existing technologies together brings a smile to my face every time.
There's an infinite variety of cool stuff we can build, but what will have the biggest payoff for my time now, what can I and my team members execute best on right this moment.
Although this is true, I think it is missing the point. What was the problem text messages was trying to solve?
Responding to a phone call on a train during rush hour. Saying "I'm almost there", or "Ill be 5 minutes late" without getting dragged into a conversation in a crowded public space.
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.