Split keyboard. Far enough apart and you have a dedicated cat zone.

Rebuttal exhibit A: https://imgur.com/a/Eu8zKMm

Split keyboard mounting each half to the chair and VR headset instead of a monitor. That way, they can't get in front of the monitor or walk across the keyboard.

A frmr coworker of mine wrote a Linux kernel module (not an April Fools' joke) to detect and prevent feline input... either stuck or neighboring keys. I don't think it was ever merged.

Saying "out of step" rather than "out of touch" seems like a bit of a Freudian slip.

Okay unless you're doing numerical analysis where they use it for the growth rate of the error term, which has nothing to do with cost or algorithms

Why would I use a Pydantic model when `TypeAdapter(MyDataclass)` exists?

Here’s the real rebuttal to my overconfidence in LLMs. Thanks for the link!

Could you avoid eval by having a CSP mode that forces reactive expressions to only allow functions users have registered with datastar in a lookup table?

Counterexample with just local signals: https://data-star.dev/guide/getting_started#data-on

You think the difficult part is merging observations with the last forecast? I guess it's a very underdetermined problem, but isn't the loss function (compare the forecast grid with later observations) the same whether you're doing grid_t0 -> grid_t1 or (observations, grid_t0) -> grid'_t0 -> grid_t1? I don't know enough about ML to know how much complexity the extra step adds, but doesn't seem like a massive difference.

Observation assimilation is a huge field in and of itself. Observables have biases that have to be included in assimilation, they also have finite resolution and so observation operators need to be taken into account.

If the FFI is also capability gated why can't the language do it?

Edit: Pony seems to rely on restricting FFI privileges at the package level https://tutorial.ponylang.io/object-capabilities/trust-bound.... Suppose it could have been function by function ("unsafe") but this sounds fine. Not sure what else I could have meant by a capability gated FFI.

In practice it means no redistributable native libraries or binaries.

You would need installation time compilation, jittin or pure interpretation.

Or some sort of trusted compiler-as-a-service with signed binaries.

euler angles aren't cool any more