Makes sense to me. The new coding agents are drastically changing software development, and I think there's a lot of space for innovation in how version control tooling works in this new world.

Why should ai need this? A linear backlog is enough, a cache, for everything else they can create it new in a short time.

Another commenter explained it: It's about working on multiple branches in parallel. You can only check out one branch at a time currently in git - but with "but" you have all the changes just in memory so different agents can work on different branches at the same time.

Working on multiple branches in parallel is literally what Git was created for, and how it's been used since the very first version 20 years ago.

Other commenters mentioned worktrees, which let you check out different branches at the same time from a single local repo. That's convenient, but not required.

Git always supported "fast cloning" local repos as well. You just "git clone" from one directory to another. Then they are independent and you're free to decide what to merge back.

These days, agents can also fork their containers or VMs as often as required too, with copy-on-write for speed.

So that's four ways to work on multiple branches in parallel using Git that we already use.

git-worktree has been a thing for a decade+ and AI agents seem to be using them just fine in my experience. This is a solved problem.

That's not even true

Why not? Are you considering git worktrees?

Exactly, worktrees solve this problem, every "agentic IDE" uses them

I've seen this sentiment often. For example, in a discussion about slow nvm load times: "Does adding 0.5s delay to opening your terminal really affect your productivity?"

I agree that these small things are not bottlenecks to my productivity. I can work just fine despite them. However there is some intangible effect they have on my mindset when I'm working. The more "snappy" my computer feels, the easier it is to enter a sort of flow state. Small bits of friction here and there add up.

This looks great, and like it could address a need in ecosystem. Also, the admin dashboard is such a great feature of django, nice job building it from the get-go.

Thanks, appreciate it! Felt wrong to ship an ORM without one.

I believe we already saw something like this happen with the PG&E power outage in San Francisco in December. The waymo post-mortem [1] describes the outage causing a backlog of RA requests, which seems to have resulted in cars blocking roads an intersections. I would imagine they've improved the system after that incident, however.

[1] https://waymo.com/blog/2025/12/autonomously-navigating-the-r...

Charm looks good. What is the TUI library of choice for python these days?

Cool to see you here on HN! I just discovered the openpilot repository a few days ago and am having a great time digging through the codebase to learn how it all works. Msgq/cereal, Params, visionipc, the whole log message system in general. Some very interesting stuff in there.

> Am I missing something here wrt Jellyfin clients?

Unfortunately, I don't think so. I had many issues with playback on ATV using Swiftfin. Infuse works very well, so it is worth the ~$15 yearly to me. I am hopeful that Swiftfin will improve over time, they have a few dedicated developers working on it.

Which app are you using on your TV? I've had success direct-playing 4K content with the jellyfin Android TV app. On AppleTV, Infuse works well. Infuse isn't free, but it is worth the money to me.

Wanted to put in a plug for Swiftfin, which plays the formats Infuse wanted to charge me money for, but is free and seems to work well. I use it on the AppleTV mainly.

This is using the native Jellyfin app available for LG's tvOS, so you're at the mercy of the codecs available on the TV. Last time I wanted to watch a movie affected by this, I just plugged in a laptop with an HDMI cable and played it that way.

This is cool. Is there a way to call ruff’s linter? Like `uv lint`, which would call `ruff check`.

To your analogy, it’d be like `cargo clippy`

You can always use `uvx ruff check` or `uv tool run ruff check`. Though honestly I find just running `ruff check` much easier.

uv ruffy sounds funny

"The Hunt for Red October" had an interesting way of handling this with the Russian speakers. The movie starts with them speaking Russian with English subtitles, does a slow zoom into the Russian-speaker's lips, and switches to English mid-sentence.

With some elegance, too; iirc they pivot languages on the word "Golgotha" as he reads from the bible, the Latin word for a location near Jerusalem, but having a non-English/non-Russian word be when they switch made it a lot less jarring. Plus, having it be during a read-out-loud-from-book portion allowed for more measured cadence that smoothed the switch but probably would have felt jarring if the audience were parsing multi-character dialogue when it happened.

> they pivot languages on the word "Golgotha"

"Armageddon" actually. Poignant because it's a movie about a nuclear ballistic submarine. But not a particularly non-English word.

ahhh I misremembered — an even better choice!

> "Golgotha", the latin word

Isn't it Hebrew? (for example see John 19,17)

From what I have to hand ..

It appeared in the Latin Vulgate (an early predominately Latin version of the Bible), the Oxford English Dictionary has it as an Aramaic form of the Hebrew "gulgōleþ" (copied from the dictionary) or skull like hill.

I found that incredibly clunky when I saw it. Also, it's a little bit extra jarring that Sean Connery goes from speaking Russian to speaking English with a Scottish accent.

That's just how the Babel Fish works. It translates perfectly, but it tacks on a random accent.

That trick has been used in movies before that too. "Judgment at Nuremberg" does something similar. A character is speaking German, slow zoom, then a switch to English.

We're zooming into their miiiiiind!