actinium226

My recollection from trying this is that it's not so easy to find that specific nixpkgs commit. It's doable if you're determined, but it's not a 1 click thing, but my information may not be up to date.

> two builds from the same Dockerfile separated by time can result in rather different container images

This is true, and the same is true of shell scripts, but isn't it true of nix as well? If you update nixpkgs and then install something, you have the same chance of getting a new version of it as you do with the `sudo apt-get install` in the Dockerfile, no? I had once looked into using nix to intentionally install older versions of software and it was not as easy as I had hoped.

Seems like a relatively simple fix, Amazon shouldn't be allowed to tell suppliers what price they can set on their site. No one should be able to tell a supplier what price they can charge to others.

This is awesome, seems like a room I would, or should, find in a video game.

Did Claude find this on it's own, or did somebody using Claude find it?

I don't really get the comments about Spotify having a terrible UX, works fine for me.

It uses 300 MB of RAM on my MacBook. Saving 50MB of RAM in exchange for losing the ability to play lossless files isn't a trade I want to make.

Cool project though, will keep an eye on it.

If he has such a good reputation, why doesn't he write well? He never actually introduces the point of the article, he merely alludes to it in the concluding paragraphs.

> The job of abstraction as a cognitive offloader is starting to retire. Agents are taking that job.

Call me when the agents can take my high level directives and write assembly.

I'd love to see something like this but with jobs created.

Username checks out.

I tried this years ago to try to develop my ability to play by ear.

What I ended up learning is that if you want to learn to play by ear, learn to sing, don't bother with exercises like this, at least not until you've gotten some singing practice in.

When singing, you have to hear the intervals in your head before you sing them, so developing that ability to generate the intervals in your head will help you to recognize them later on.

This looks like they simply reinvented PID control. The inputs to the beyond are desired states minus actual states, which is basically how PID works.

I don't get how this is meaningfully different from doing something like:

1. Squash all your commits in this branch to one

2. Move that commit to the working directory with the appropriate git reset command

3. Commit hunks as appropriate.