[deleted]
Show HN: Oak – Git alternative designed for agents
41–50 of 216 posts
Re: Show HN: Oak – Git alternative designed for agents
#42Earlier quoted context omitted.
"I wish commits could be folded into larger commits so that you can still capture the individual changes but also not see them by default when looking at the history of a file." Fossil merges do this. More people need to use Fossil; it's got a ton of great ideas. "If I split a file in two I still want to be able to see blame correctly for the author of the function, not one file as freshly created and the other with…
> "If I split a file in two I still want to be able to see blame correctly for the author of the function, not one file as freshly created and the other with a bunch of deletes." > > Now this is a good idea that I've never seen in a VCS. There's a reason no one has done that, the VCS would have to have a semantic understanding of what it's tracking. I'm sure that's possible, but I think would see extremely limited su…
The other way is to make the tool UX do the semantic, ie:
`git split`
Something that I enjoy with jujutsu is that the semantics is the tool itself. ONCE you do that, the rest become easier!
Re: Show HN: Oak – Git alternative designed for agents
#43It's kind of like replacing Wordpress. Sure, you can make a better alternative. But replacing an entrenched player that has been there for at least a decade will be almost impossible.
Re: Show HN: Oak – Git alternative designed for agents
#44Earlier quoted context omitted.
Git is great but if you really haven't found any reasons then you haven't looked at all. From large files to sub modules to hook permissions and file permissions... The list goes on and on about what where git falls short. There's plenty of workarounds too, but that's what they are. Workarounds.
Do you know if Jujutsu addresses these issues?
jj does not have large file or submodule support, but it does intend to in the future (you can read their design docs). Right now it's git compatible, so I'm not sure how 'permissions' would be stored compatibly, or what that means. I'm guessing ownership and xattrs
Re: Show HN: Oak – Git alternative designed for agents
#45I have always wanted a version control system that was basically Emacs/Vim/Neovim's undo-tree[0] but persistent and social. Why do I have to manually talk to git? You are a computer, track every modification I make while editing and let me decide (or help me decide) on what a checkpoint is. [0]: https://i.sstatic.net/4vbd9.png
Zed’s DeltaDB is that very idea I believe
Re: Show HN: Oak – Git alternative designed for agents
#46"Git is forever" Many things were forever until they suddenly died, but I think this is especially true for git. I'm not saying this as a git hater, quite to the contrary. I think git is great. I also think git is an ill-fit for the majority of modern commercial software projects and there will be a breaking point where companies realize that and move on.
What is git not suited for in modern development? I haven't found any reasons.
Game development, with very large assets. Also, git is pretty terrible with non-text files.
Re: Show HN: Oak – Git alternative designed for agents
#47It's kind of like replacing Wordpress. Sure, you can make a better alternative. But replacing an entrenched player that has been there for at least a decade will be almost impossible.
you don't need to replace, you just need to find your niche, then expand from there
Re: Show HN: Oak – Git alternative designed for agents
#48[flagged]
[dead]
Re: Show HN: Oak – Git alternative designed for agents
#49seems like an interesting idea. the only friction would be to get people to use it instead of git, however i believe it will happen slowly, more people trying it and recommending it to others.
Re: Show HN: Oak – Git alternative designed for agents
#50I've built my own workflow for using agents on git, as i now often have to do changes across repositories, or in the same repository for different tasks. I could use worktrees, but I'd rather invert it, give agents the ability to have a workspace, that they pull repositories into, create branches as they want, commit on main it doesn't matter. the agents don't bother each other, and when i finally have to merge, conflicts are either resolved, or it is just smooth sailing.
The tool is called gitnow. it is honestly quite simple, just create a project, add the repositories you want and get to building. I've found having another claude chat or whatever use the tool to great success coupled with zellij, but could also be zed, tmux or whatever.
Secondly it also pretty much solves the problem of the agent dumping memory files everywhere, they now basically have a scratch space that is theirs, where they can keep their tasks, and just update the repositories as needed.
Use gn the shell after eval if you use it, it will actually invoke cd, instead of creating a subshell.