HN user

MForster

631 karma
Posts7
Comments37
View on HN

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)

Jujutsu for busy devs 12 months ago

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.

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

Is it because of the enemies?

FWIW, you can turn them off. I always play with them disabled. Just not what I'm interested in. You might enjoy that, too.

I also enjoyed shapez, but it's no comparison to the depth of Factorio, especially with mods.

Thanks for pointing out the encryption. That changes things a bit, IMHO.

Would have been nice if the article explained a bit what is actually happening. The wikipedia article doesn't mention it either...

Sorry for coming across as using bad faith. It's just that I didn't understand the overall model. And the article didn't explain it.

Also, I wouldn't blame the victim. I'd rather blame Apple for making their users opt in.