If it's really so for some people, a case could be made that their problems can already be half-solved by changing the granularity of their commits: just commit more often.
I disagree. JetBrains PyCharm has a similar "local history" feature that solves this very real and existing problem and has saved my ass more than once when accidentally overwriting changes before committing or fubar'ing a git reset.
1. Commits are really just manual checkpoints while you’re working. Why not automatically checkpoint everything so you can actually go back to an older implementation without needing to remember to commit it?
2. Agentic workflows are so deeply single player. It’s very annoying, I want to collaborate with my team with agents, not review the output of one dev’s agent which they’ll just shove back into their existing agent.
I find that it better surfaces the best discussion when there are multiple threads (like in this example), and it keeps showing slightly older threads for longer when there's still discussion happening.
On behalf of everyone else in the world, please invest in headphones.
Broadcasting in this way is boorish and the kind of thing emotionally stunted people do to inflict their will upon others. I'm not saying you're necessarily like that, but you're 'wearing their uniform' so to speak.
Cargo absolutely uses git, or else we wouldn't've had that thing where setting it to use the cli git instead of some reimplementation lead to massive speedups
What I mean is that it doesn’t use git as the source of truth for packages (unless you point at a git repo instead of crates.io). It does use a git repo for the index.
What they meant was probably, that you have the option to rely entirely on using git repositories for your dependencies or even just paths to other projects on your disk.
You can also setup your own dependency registry and only work with that.