alright2565

[1]: https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-va...

is load bearing I expect.

> All Rights Reserved

unfortunately

This is the crux of the issue. It's really unfortunate how botched the rollout of chip and contactless payments in the US has been, magstripes should have been completely eliminated a decade ago.

The UL mark is valuable, as are the other test lab marks. However, while an ethical storefront would require it, Amazon does not. I've bought plenty of things that are not listed, and if I want safe products I generally have to include "UL" or "ETL" in my search. Even that doesn't always work, I've seen products on there claiming a listing in the title but photo shopping the place where the UL logo ought to be off of their product images.

If only :)

This should work, but glibc has a bug where it doesn't support communicating a link-local scope ID in its name resolution subsystem. So you will have to first manually resolve the name, and then use the IPv6 LL address with scope ID directly.

With micro services, that same function call is now a minimum of 200us. And now I have LOC for serialization/deserialization, retries, error handling, etc, bloating my code and making it harder to understand, plus now to do the same integration test I need to understand N different build systems for each component.

    post-build-hook = .../upload-to-cache.sh

    #!/usr/bin/env bash
    set -euo pipefail
    set -f
    export IFS=' '
    exec "${NIX_CACHE_NIX_BIN:-nix}" copy --extra-experimental-features nix-command \
      --to "s3://my-cache-bucket?region=us-east-1" $OUT_PATHS

Once a data center shows up, that plot of land is locked out of more productive development for decades.

If nothing else, the Sunshine Request site is a good place to get form emails for these requests from.

I don't understand what you mean. Doesn't smearing still mean the clock only goes forward? It's still steadily incrementing. The only difference is that a second is slightly longer/shorter than you expect, but you already have to account for that if you're doing the kind of physics experiment where it would matter.

If only we had research on the effect of a second or two's effect on user experience.

I wouldn't have a problem with it if it was on expensive endpoints like search or deep history dives, where it matters for server load. But it's every single page, out of some strange sense of righteousness.

Money anti-counterfeiting is trivial, it's just 5 dots arranged in a specific pattern. Deciding what is a gun part is impossible, even for an expert human.

Claude needs good variable names a lot less than humans do, so renaming/typedefing doesn't seem to be as necessary.