The sentence that you quoted is more generic. The Zig issue is only one example of "some reason".

You can't unsubscribe from this because it is not a normal service, but a racket. By definition: a service that creates its own demand.

It also equals x with appropriate assumptions (x > 0).

Well, then sin(x) = x if x is infinitely small

> Assuming[x == 0, Simplify[Sin[x] == x]]

Mathematica returns True. And any middle schooler will also tell you it's true.

The only reasonable interpretation of "infinitely small" is that it's zero.

sqrt(square(i)) != abs(i)

So no, it’s not unconditionally correct either.

You are talking about spatial safety. There are a few other types of memory safety:

- temporal safety (e.g. no use after free) - initialization safety (no read of initialized memory) - thread safety (no data races) - type safety (accessing memory with the correct type)

> The main things that drives me crazy about jj is that all changes are always staged implicitly.

That's one way to look at it, but I would encourage you to think about it a bit differently.

JJ does not have a concept of "staging", it only has changes and commits. Yes, it automatically snapshots the workspace commit, but I wouldn't use the workspace commit as your staging area. If you want to do explicit staging use the parent commit (@-) as your staging area. You can move changes from the workspace commit (@) to the staging area (@-) explicitly, just like in Git. And you can "commit" (Git terminology) your staging area by starting a new staging area.

The difference here really is "only" that the workspace, the index, and committed changes are modeled with the same concept. And that is very powerful. Admittedly you have to make an informed decision on how to map your workflows onto the model, but that is what comes with the powerful flexibility that it gives you.

You don't even need to re-clone. You can add jj to an existing git repo.

The CDU has moved from very right to less right, but still right-of-center under Merkel. After Merkel they have moved back right, maybe even more than they were to compete with the extremists.

It's quite the opposite. This is intended for engineers to make good trade-off decisions as a rule of thumb without financial micromanaging.

You can still use a similar workflow as with the index. The difference is that the staging area is modeled as a commit, so it's not another concept that will take a while to grok.

Same with the working copy.

> Sapling supports cloning, pushing, and pulling from a remote Git repo. jj also does, and it also supports sharing a working copy with a Git repo, so you can use jj and git interchangeably in the same repo

As a minor update - sapling now also supports the .git on-disk formats so that you can use git and sl interchangeably in the same repo