Their working is exceptionally thorough, all the concerns about additional maths and transformations is well considered. I really have to wonder if introducing any semantic-changing transformations for what I’m guessing are minuscule savings of bytes is worth it though. Safe things like stripping white space and shortening identifiers would be the major contributors to minification surely. How many CSS colours need to be defined for oklab rounding to even affect how many tcp packets are sent for instance?

Python too under the hood, a lot of its core is still from how it started as a quick way to do unixy/C things.

I don’t lose bags either, but airlines do. The AirTag let me tell United which building in Houston in ended up in (after getting lost at SFO), and refute their gaslighting multiple times that it was heading my way. Worth its weight in gold, literally.

While it’s hardly insightful that SQL is useful, I would have liked to read more about what the actual workload involving duckdb on a local machine looked like. I’m fully on board that local or single vm workloads can do an awful lot, but I’ve never been particularly satisfied with the pipelines I’ve seen (including my own). Usually they’re piles of scripts and intermediate data files sitting around and are hard to make idempotent and understand if you aren’t the author.

Also fwiw there’s no such thing as an M4 Ultra chip. That detail was either a mistake or hallucinated.

I’ve spent a lot of time with both, and hands down the wired one is far more flakey. Granted I think that’s more a Mazda software issue, but a solid 10% of the time I get “CarPlay failed” and the only way to fix it is to turn the car on and off. Never once had an issue with wireless in a Hyundai.