ec109685

Their model is to have a persistent server running.

cmux is fully open source and open to contributions. I have worked on its tmux mode a bunch, and I find it good now.

I remember you asking for a contact Apple in the army days to replace their terminal's engine. Hoping it happens in 28.

If I were Apple:

  1) All parsing of hostile input happens in micro VM's
  2) Re-write as fast as possible the core in a memory safe language

What do you see as the main advantages of gvisor instead of working within a lightweight VM with full native performance?

As the container escapes with K8s shows, it is super tricky to get isolation right. E.g. what happens if a file you think is safe to write to is suddenly is replaced by one that isn’t.

I was expecting something much more rigorous than a few trials resetting the controller at random points in its update process.

> to me this shows the importance of human in the loop

What part of the tos is violated?

They can’t decrypt the thinking traces.

Fable is still the best there is. Sol close second but I find it gets way to stuck on details.

Also Opus 5 is fine if your codebase is simple.

I spent $800 in a few hours when my sub maxed out because I was trying to get something done and had a long car ride to let it churn.

Their api pricing is absurdly expensive.

> The bug is a data race with tight timing constraints. It is unlikely to occur in common use. The developers have never been able to reproduce the bug organically and had to add special testing logic to SQLite that deliberately triggers the circumstances of the the bug in order to verify that the issue has been fixed.

I read that and it feels like some theoretical thing versus causing impactful outages for workloads shaped like tailscale’s.

Tailscale isn't mentioned in the SQLite changelog.

I agree it's tricky, but Tailscale had downtime by this bug and the SQLite Changelog downplayed it.

While technically true as written, it seems to downplay the significance:

> The bug is a data race with tight timing constraints. It is unlikely to occur in common use.

A large customer did experience this corruption, so it's important for people with tailscale's setup update immediately.

> The developers have never been able to reproduce the bug organically and had to add special testing logic to SQLite that deliberately triggers the circumstances of the the bug in order to verify that the issue has been fixed.