In a similar way to how a radial burn (https://space.stackexchange.com/questions/44608/what-happens...) may be orthogonal to your trajectory but still may be necessary to avoid becoming a fireball in half an orbit's time.

Any chance of supporting some of the new gen OGC APIs (https://ogcapi.ogc.org/) vs the old WFS, WMS etc?

Would be quite compelling if the CLI worked with nushell.

I see the (a?) backend is polars, which is good as well.

This in CLI might be the quickest / tersest way to go from "have parquet / csv / other table format" to "see graph", though a keen polars / matplotlib user would also get there pretty quick.

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?