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.

The US has tested more than 2k people each day since March 8th. This is just wrong and misinformation at a time like this is really really dangerous. https://www.cdc.gov/coronavirus/2019-ncov/cases-updates/test...

"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.

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.

http://images2.wikia.nocookie.net/degrassi/images/9/90/Thats...

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.

This seems a little alarmist

this is the coolest thing I have ever seen

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.

The cellphone was very much a utility for a large portion of the mobile market before the iPhone came along.

This app is amazingly helpful. And as someone living on my own for the first time (and thus grocery shopping completely independently) I have definitely bookmarked it.

Just a quick question from someone who has worked on a similar app before. How are you importing word documents? When I was working on something like this every solution was either extremely convoluted or very unreliable (AbiWord was basically all I could find).

This runs into issues when the code relies on anything outside of the lib/ directory. This is because Rip only copies the lib/ directory (and bin/). Bug reported http://github.com/defunkt/rip/issues#issue/25 and being worked on but I wanted to give the heads up.

"Bad programmer writes bad code"

This is hardly a new idea. The fact that a bad programmer used Ruby on Rails, or Django, or PHP, or C++ to write bad code and implement it on a shoddy system is no reflection on anything. This is essentially a story of someone who took good advice for a hosting environment, and someone who took bad advice for a hosting environment.

Learn your tool, don't buy into the hype. Make sure you are aware of the reason behind everything that you do (because they I read it on a blog is not a reason). Don't be a bad programmer.

For someone who is angry about the UI of the AA site, the UI of your own site could use some work. I can not click on any of the pictures, and instead I am forced to click a giant "See the redesign" button. I also can not click on your logo to get back to your homepage, even if I wanted to hire you I have no idea how to get to a page that will tell me how.

The page appears to be down for me.

http://downforeveryoneorjustme.com/http://nrds.co.uk/