418 karma · joined February 20, 2014
Or put another way, they have two products at different levels of the stack and they have consciously chosen to risk one (the game) to leverage all their customer’s of their other product (Unreal Engine) onto their side in this war.
The most common, and automatic, is the verification of the chain of trust. On iOS this happens automatically if you use the standard network APIs against an HTTPS URL.
You can take it a step further and avoid MITM attacks where the middle party is able to mint trusted certs by doing something called certificate pinning. This is a manual verification that the certificate used by the server you’re connecting to has certain properties that you know match your API server’s.
https://developer.apple.com/documentation/security/complying...
> in our Body Warn Camera page, https://www.eff.org/pages/body-worn-cameras,
Warn vs worn
> This means that the core features and functionality of the app must be contained within the binary of the software, rather than made possible by referring users outside of the approved app, including through the use of HTML5.
This feels like a sort of race to the bottom.
Is it `/width/height` or `/height/width`?
To me this is very similar to languages that use names parameters vs positional.
Richard M Stallman.
I’m interested in why this CEO/company thinks their solution is better?
How will they protect their advantage (or rather, how is that advantage protected)?
https://www.theverge.com/2018/11/30/18119576/pewdiepie-print...
Codable is desirable because it encodes/decides directly to strifes vs manually picking fields out of dicts.
That said, I have to check those out you mention (never heard of any of them). Thanks.
My current personal favourite is Hasklig.
TypeScriot has a lot of features and the time to move those through standardization and then runtime (and browser) implementation is nontrivial.
If TS runs stalls and doesn’t innovate it _could_ happen, but like I say, subsiding all of those features into the base language would be a win for everyone.
> @orta already answered here, but the tl;dr (at least to me) is that the point here is to make the code base more approachable to to new (and old) contributors who are consumers of Jest. The vast majority of them are JavaScript developers, not OCaml developers.
The book is: Mr China by Tim Clissold
The other was a plane made with a drinking straw and two paper rings. It always flew really far also!