HNHacker News
TopNewBestAskShowJobs

ersatz-matty

8 karma · joined April 14, 2026

submissionscomments
ersatz-matty··on How accurate have Ed Zitron's AI skeptic predictions been?
> I don't benefit in any particular way if AI does well, except insofar as anyone who holds broad index funds benefits, but I do care about accuracy.

Does Dan Luu still work at Nvidia?

> I had ChatGPT give me a list of predictions (with no attempted tilt towards correct or incorrect predictions) and then I skimmed/read the posts that ChatGPT linked to.

yeah alright

> If I really thought about it, I probably could've found something better to do with the time

Extremely likely.

> And yet, it would seem that my fact checking process is a lot more thorough than Zitron's.

Dan says in his post he fact checked with Chat-GPT and Claude, so: lmao.

ersatz-matty··on Grit: Rewriting Git in Rust with agents
That's great because we don't.
ersatz-matty··on jj – the CLI for Jujutsu
`jj undo` compared to what exactly?
ersatz-matty··on jj – the CLI for Jujutsu
In practice, it isn't. What you're identifying as potentially nightmarish - and no doubt quite tedious in git - are things that JJ enables you to do with a small subset of commands that work exactly how you expect them to work _in every workflow context_ in which they are needed.

Thinking specifically about conflicts: being able to defer conflicts until you're ready to deal with them is actually great. I might not be done with what I am actually working on and might want to finish that first. being forced into a possibly complicated conflict resolution when I'm in the middle of something is what I'd actually consider nightmarish.

When you want to solve the conflict: `jj new <rev>`, solve the conflict, then `jj squash`, your conflict resolution is automatically propagated to the chain of child commits from the conflict.

ersatz-matty··on What is jj and why should I care?
Consider using the table of contents on the left of the page to view "Real World Workflows", "Branching, Merging, and Conflicts", and then "Sharing Your Code with Others" and then evaluate how JJ does things against your current git workflow. This requires some minor effort on your part.

The official JJ docs also have a "bird's eye view" introduction and tutorial available here: https://docs.jj-vcs.dev/latest/tutorial/.

EDIT: Jujutsu for Git experts: <https://docs.jj-vcs.dev/latest/git-experts/>. This outlines some of the main advantages relatively succinctly.

ersatz-matty··on jj – the CLI for Jujutsu
From your "polluted" snapshot, you can run `jj commit -i` and use the TUI to select only what you want.