nroman

> small shop

Like Facebook? Netflix? The BBC?

Anyone know if the IAM roles and security groups are applied at the individual container level or at the instance level?

In practice it wouldn't make much sense to cache whole query responses to GraphQL queries because your hit rates would be too low due to the variability of the queries. You end up pushing a lot of the caching to the client. That's not really a big issue because if you're writing something like a Android or iOS app because you already need to be caching lots of data on the client-side to make the app responsive.

On the server you end up caching at lower levels in the stack. For example a query for user(id: 123456) {id, name} is going to need data from a key-value store containing user info. That access can easily be cached with something like memcache, saving load on the database. Cache-invalidation problems are also much easier to solve at these layers.

As an ex-Facebook employee, I can't wait for this to be released to the public. It is hard for me to overstate how much this infrastructure makes building products a joy, not to mention the tremendous developer and server efficiency that can be attained. I miss having the GraphQL stack so much when working on my own stuff.

The client application should drive the decisions about what data to fetch. After all it's the client that knows what it is actually going to be doing with the data, not the server. Current approaches like having a "fields" option on a REST endpoint are at best a hacky approximation to this.

If you do in SASS

  .Foo {
    a {
      /* stuff */
    }
  }

It translates into:

  .Foo a { /* stuff */ }

CSS is evaluated right to left, so this means every time an <a> is encountered in the page it has to at its parent chain to see if any has class Foo. This can cause performance issues especially for really large pages.

That said, for most pages it won't make a noticeable difference so it's kind of up to you to decide if you care.

In other financial news, Twitter shares fell 7.2% on the Oculus deal. Tesla lost 3.4% on the Oculus deal!

</sarcasm>

Anyone know of a good place to download stats? They don't have to be live. It'd be fun to build some analysis tools.

Alternate title: How to self-XSS your Facebook account.

These pie charts are bad. You shouldn't have the same browser switch colors as you go through the charts. IE starts as purple then is blue; Firefox makes it from blue to purple to red.

Please, for the love of the web, implement browser history management so that I can use my back button.

In college I lived in an old apartment building that had been updated to have 3-prong outlets. One day I was wiring up some audio equipment for a party. As I hooked my computer to a a receiver in another room the audio cable immediately started sparking and the rubber insulation melted off. I yanked it out of my computer. Luckily the only real damage done was the sound card for my computer and the destroyed cable.

Later I did some investigation. First I bought one of those standard outlet testers. It seemed to suggest that everything was fine with the outlet. Then I did some more investigation. I got a volt-meter and started measuring the voltage from the different prongs. Finally I measured the voltage compared to a copper pipe in the house.

Turns out that both the neutral and ground wires were actually hot (as measured against the grounded pipe), and the "hot" wire was the ground. The outlet in the other room had been wired correctly. The shielding on the cable was grounded so suddenly it sent 120 volts down the audio cable when I plugged it in—destroying it in seconds.

The electrician didn't believe me when he came in to fix it, but was finally convinced when he checked against a pipe.

Just goes to prove that you can't make any system fully fool-proof.

Good luck. Hope to see you soon!

-Roman