This helps on both ends of the cost spectrum. Large 64 core instances are where our heuristics fall off the most as variance increases, & tiny instances with 8GB of memory can use every 100MB of RSS we can get
5,734 karma · joined September 12, 2015
This helps on both ends of the cost spectrum. Large 64 core instances are where our heuristics fall off the most as variance increases, & tiny instances with 8GB of memory can use every 100MB of RSS we can get
Can't win the lottery if you never buy any tickets
His mistake was making _all_ reference taking functions also accept null. In Rust functions opt into None | Some
This comes up with C# which must have default(T) so references default to null. In Rust there is no general default(T) that must always resolve
Next up, "millions of malicious packages still not taken down on internet"
My issue was tendon overuse in my fingers, so low force switches & column splay worked for me
(splay is where the columns are not aligned, mapping to the fan out of the human hand, see TOTEM https://github.com/GEIGEIGEIST/TOTEM)
I've always hated stateful control. Always ripped out caps lock key from my boards (or later figured out remapping), same for insert mode
That's carried over, even with options like one shot mods, & cutting down to under 40 keys (& playing with 28, yesterday received a https://github.com/kilipan/zilpzalp), I still don't find stateful control necessary. More layers, combos, & tap-hold go far
tattoo yourself with crypto code to become munitions
This f’n Karen decides to come over to my desk and tell me it’s “inappropriate” and “gross” and “ur mom’s placenta will get in my salmon salad”.
Win for me: keep wearing the shirt Win for Karen: stop having me wear the shirt Win Win Win: frame the shirt on my office wall so there’s never a chance of getting placenta in Karen’s salad.
Win Win Win!!