HN user

jalk

837 karma
Posts2
Comments382
View on HN

You have to put them in pairing mode first: For airpod pros: Open the lid, keep the earbuds in the case, double tap your finger on the case just below the green led, The led should start to flash white and the airpods now appear in the device list in linux so that you can pair with them. Non-pro have an physical button on the rear IIRC.

How uv got so fast 7 months ago

There is definitely also a manager dick-measuring contest based on headcount, going on in large orgs.

Not sure what you mean by cryptographic strength - they are both Unique ID generators, not meant for anything related to cryptography.

UUIDv7 has 62 bits of random data, ULID uses 80 bits, so if anything ULID is "stronger" (meaning less chances of generating the same id within the same millisecond)

I've heard that a major hurdle for these "cell-factories", is moving from lab to industrial scale. Ofc initial cost of the product is typically also a lot higher, but that is the same of any product addressing externalities of existing production

Thanks, I see your point. Was not trying to be snarky/funny, but rather come with counter example to parent. I was thinking about the (recent) "Era of globalization" - but perhaps that is too short of a time span to be called an era

[1] shows that they their coal plants have not been sitting idle i 2025 and are producing close to what they did in 2024. [2] shows that coal based electricity produced is still increasing, but their overall CO2 emissions / kWh is lowering [3]

[1] https://ember-energy.org/data/electricity-data-explorer/?ent...

[2] https://ember-energy.org/data/electricity-data-explorer/?dat...

[3] https://ember-energy.org/data/electricity-data-explorer/?dat...

You must have some other sources than that site. Downloaded the CSV, and at the risk of misinterpreting the columns here is some simple filtering:

% of total energy generation

  EU Coal   9.64%
  US Coal  14.88%  
  CH Coal  57.77%

  EU Solar 11.19%
  US Solar  6.91%
  CH Solar  8.32%
Largest generation source
  EU Nuclear 23.57%
  US Gas     42.51%
  CH Coal    57.77%
This ofc only says something about generation and not consumption

I was thinking about basic tool use. I expect a junior engineer candidate to wield a computer way better than my mom. They are applying for a junior engineer position not and apprenticeship starting with close to zero training. I have no problem with candidates who stumble and make awkward choices during the interview, as juniors by definition lack experience and the interview process is a stressed situation.

Some points in parent comment are absolutely valid IMO. Would you hire a carpenter who walks back and forth to his toolbox to pickup at single nail at a time and then use the hammer with both hands near the head. And when cutting a 4x4 beam will use 1-inch strokes with the handsaw (again with two hands).

That was the extreme case - the multi-scan would be gotten if a casual reader tried your (neat by all means) AND-only query on a non-indexed table (or partially indexed for that matter).

Can we agree that this is only applies to queries where all the filter conditions use cols with indexes? If no indexes can be used, a single full table scan with OR surely is faster than multiple full table scans.

Havn't tried Colima, but podman is very simple to use and smells like docker cli.

On Apple Silicon machines however, latest podman version uses VM images which Rosetta doesn't work with, and hence it will use qemu for running amd64 containers. You can fix this by either installing podman 5.5 or create the VM from and older image [1]. My only complaint here is that the stock machine images are pretty large (~1G )

If you use containers to run tools that create files in your host (i.e. build tools), then you can use your host username as the default in the VM (machine init --username $(id -un)), and then run containers with --userns=keep-id. That way the the container command starts with the same username and uid as you host user - this is pretty tricky to get working with docker, from my experience.

We use Bazel as our build tool and we create a lot of images based on shared layers. Bazel produces oci layout directories that contain descriptors and symlinks to the actual layer tars. Podman can start a container "directly" from these directories[2], which speeds up image testing considerably, since it can detect known layers immediately. With docker you have to stream a tarball with all the layers and descriptors to the docker daemon, only for it to discover that it already knows most of the layers.

[1] https://docs.podman.io/en/latest/markdown/podman-machine-ini... - machine images https://quay.io/repository/podman/machine-os

[2] podman run oci://<path to oci-layout-dir>

in my homedir

  > fd -t d | wc -l 
  213842
takes 5 seconds.

Population doing `cd ~/**<tab>` takes way way longer than 5 seconds though.

But regardless of the speed up one could add to cd + fzf in this case, I will still be using zoxide:

  > zoxide query -l | wc -l
  1294
and `zi` starts instantaneous if I need the dynamic filtering

edit: layout