alt Hacker NewsRift: Better Alternative to Git Worktrees
Comments
Brought to you by the infamous author of yet another llm harness - will exfiltrate all your data, then feign ignorance:
git worktree (or any COW snapshot like this) still leaves you reinstalling node_modules per tree and fighting over a dev server port. That's the actual cost, and none of these tools touch it. So I gave up on parallelizing inside one repo. I run agents across different projects — one repo each — and stay serial within a single project.
Is it just an experimental tool by opencode team? If there is some article about this tool, I would love to read it. It’s not clear to me why I should use this instead of git worktree.
Currently it just sounds like an alternative to work trees, but with no explanation on how it’s better. Seems early stages, use of btrfs is cool, but unsure why I’d use this right now
I find it hard to understand what it is about. Better in what way?
If that achieves quick COW copies of whole repo and works on Mac OS that's the solution I've been looking for last few weeks. Internets and Claude were insisting that such copies are possible only on Linux via OverlayFS. Seamless switching between unrelated features in the same repo – here I come!
Neat! Would a similar approach work with ZFS instead of btrfs?
Does it work well when we have gitsubmodules?
I had some issues regarding that.
Will this replace /warp in Opencode? Seeing as it's made by the same team
[dead]
[dead]
Readme seems generated then minimized to the extreme, to a point where I cannot follow it anymore.
> The JavaScript init function initializes exactly `at`; Git-root selection and `--here` are CLI behavior.
What does this mean? Maybe I'm missing something
Also some of the stuff in this README seems like it should be in comments above/in their respected code blocks.
It also did not tell me why rift is a better alternative. Because it's fast? git worktrees are also fast.