1,056 karma · joined May 10, 2013
Admittedly it’s rare, and personally I wouldn’t be worried about it as a liklihood.
I think my friends recognize me thank you very much Facebook, otherwise they're not, you know, my actual friends?
The reason being Docker for Mac uses a VM anyway (an xhvye machine) - it does try to hide/abstract this away, but inevitably this leaks. The xhyve VM has the usual parameters memory, diskspace, CPUs, and not least a kernel. There are limited options to fiddle with these parameters, though you can log into it and poke around there. I thus find it easier to just have setup Vagrant machines with Docker - then I have better control over those things.
If I were on a Linux distro though, I'd probably use Vagrant a lot less.
It's curiously satisfying (I suppose because it's affirmative) to see one's subjective experience described objectively like this though.
javascript:window.location=%22https://m.facebook.com/l.php?u=%22+encodeURIComponent(window...;
E.g: https://m.facebook.com/flx/warn/?u=https%3A%2F%2Fwww.washing...
Also, would a custom UI like the Letterpress game (which as I understand it used a custom OpenGL UI), use a similar technique to this? I'm unclear how subpixel rendering works in the 3D context.
1) Search JSTOR: https://www.jstor.org/action/doBasicSearch?Query=proofs+and+...
2) Use Sci-Hub to download it (handy bookmarklet): javascript:document.location.hostname=document.location.hostname + ".sci-hub.cc";
If you end up putting that on the server anyway, you're back to fixed responses, no better than a REST API.
"The native app teams discovered that using GraphQL came with the additional overhead of building queries by concatenating a bunch of strings and then uploading those queries over slow connections. These queries could sometimes grow into the tens of thousands of lines of GraphQL. Also, every mobile device running the same app was sending largely the same queries.
The teams realized that if the GraphQL queries instead were statically known — that is, they were not altered by runtime conditions — then they could be constructed once during development time and saved on the Facebook servers, and replaced in the mobile app with a tiny identifier. With this approach, the app sends the identifier along with some GraphQL variables, and the Facebook server knows which query to run. No more overhead, massively reduced network traffic, and much faster mobile apps."
Firstly, what query could be 10k lines? Secondly, if you're defining the query just by an id, how is that then any different to a fixed REST endpoint or stored procedure?
"What United and all companies need to do is to train and empower workers to deal with specific issues as they arise,” she said. “Don’t just follow whatever is written in your policies."
Unfortunately that's so often the case - one may as well be conversing with a robot in many customer service situations. I can only imagine it's just as frustrating for the disempowered service reps.