1,081 karma · joined December 21, 2018
...except you can't? Not sure where these assumptions come from.
Apple has built iOS off user trust & goodwill, unlike most other OSes.
For Dan's suggestions, the IIHS already breaks down death rates per 10 billion miles by vehicle class and individual vehicles, and the latter supports the original ordering by registered vehicle years. Also, incorporating data from models under the same make doesn't make sense. Since the IIHS already accounts for different vehicle platforms, any believed correlation in death rates between a manufacturer's models must derive from the original dataset, creating a meaningless statistic.
Updated IIHS doc here: https://www.iihs.org/api/datastoredocument/status-report/pdf...
Better known as PayPal?
> Overpromised and Underdelivered
Sounds kind of catchy, to be honest.
I'm with you on AOT, but I think the language makes more sense if you understand it as a .NET port of OCaml. If you isolated F# from CLR, you'd lose libraries and tooling, arguably F#'s raison d'etre, pleasant design choices aside.
Mind elaborating? F# seems like a decent fit from what you've said. I'm hoping the language will grow less stagnant as .NET Core matures.
Elchemy, Alpaca, and Gleam try bringing static typing to the BEAM, but they're still too immature, unfortunately.
Trivial quibble, but Cao Yuan's the first author and lead researcher for these papers and unfortunately not directly mentioned -- I heard he had to argue for taking this approach to graphene.