anlsh

Man what a beautiful bit if knowledge, reminds me a bit of the eel mystery. Thanks to the researchers doing this sort of work, and I hope their conservation efforts go well

This is a public service announcement: please stop barbecueing your jackfruits, this is a culinary crime beyond even boiled vegetables. Please, for the love of god, just eat something fresh for once in your life

wikipedia's explanation works for uniform bodies, yours doesn't. And since tidal bulges seem to be symmetric, there's no away to explain away the deformation as making one side heavier

Oh neat, a post I actually know something about! I worked a lot on userfaultfd performance for GCE's live migration post-copy a couple years ago. Or more specifically, I worked on mechanisms to avoid it entirely- due to lock contention in the kennel, faults become veeeerry slow as the number of vcpus scales, and as it happens VMs these days can have a lot of vcpus

What an arrogant and slavish comment. Truth may be the first casualty of any war, yet here you are celebrating its demise so that war may be waged more thoroughly.

I wonder what it's like to be so convinced of your righteousness of your cause that reality itself is seondary. What a joke you are.

If anyone works at bitwarden can you get your UI people to stop retheming for the upteenth time and instead make the "detailed view" of any entry read-only by default? Every time I need to access my notes on an entry I'm scared that I'll accidentally typo a letter into my password or a 2fa code or something

Not at all, think about it

A very plausible explanation is that the separation was biotic

Why does a password-protected zip file reveal a list of the files within lol?

If I'm understanding this right, we'd have been hosed if the files had been TARd first?

Ok now we're talking: important clarifications. Neat read on the type systems. But this part is extremely important:

> The idiomatic way to do it is to allow garbage inputs like negative numbers into your square root function, and return garbage outputs. It is in the theorems where one puts the non-negativity hypotheses.

The equivalent condition here would be for everyone to include "zero-ness" checks on their numeric inputs. But that's awful, because whereas everyone agrees that nullptr is a meaningless pointer, zero is in fact a perfectly good integer/float whatever. So now you have something worse than null pointers- which have course caused us a huge amount of pain ever since being inflicted on the world

So x / 0 = 0 is still a terrible, terrible, idea. But introduce something like the floating-point equivalent of NaN, and say x / 0 = NaN, and now your outputs will at least be obviously wrong, instead of just silently wrong