zdgeier

8 ms·

1.
by zdgeier 1mo ago
We've added some things like CI, Windows support, and starting some work on path-based permissioning for monorepos. These are still in the early stages so not documented that great yet and need to be tested a little bit more. Should ha
2.
by zdgeier 1mo ago
I’m building a non-git alternative https://oak.space Would love for anyone to check it out!
3.
by zdgeier 3mo ago
Do you think it's possible in the next few years or so that agents will improve to the point that some of approval work can be offloaded to them?
4.
by zdgeier 3mo ago
True, I do wonder if we focused more on the parallelism aspect with mounts that it would resonate with people more. Thanks for the thoughts!
5.
by zdgeier 3mo ago
It's also made for humans as well :) We have some nice TUI stuff in the CLI that you might like. Check it out if you're curious and let me know if you have any thoughts.
6.
by zdgeier 3mo ago
Agents in the cloud (and locally) need to have a full repo, even if they only need a small percentage of a repo to make a change. You can also imagine if changes are being made in the cloud by multiple agents, each one of these agents need
7.
by zdgeier 3mo ago
Mostly through networked file system mounts with FSKit/FUSE backing when working on tasks in parallel. May be applicable for human facing tools but I think workflows there are already pretty set with having files locally and mounts nee
8.
by zdgeier 3mo ago
Happy to describe or answer questions here. It's a version control system (like Git/GitHub) designed for agents. Some specific things that make it different than git are a simplified branching system and networked mounts so you ca
9.
by zdgeier 3mo ago
I do think hosting is an important part of the VCS story. I agree that hg and jj and sapling are capable of being front ends to a google3 like backend GitHub like thing to support it (Google has this internally for jj). Of course some peopl
10.
by zdgeier 3mo ago
A good tingle or bad tingle? haha
11.
by zdgeier 3mo ago
Good question, the files are grabbed on demand from the server so the agent can fetch everything it needs to run tests, a dev server, or anything it does normally. Now this might be slightly slower in some cases where the history is short,
12.
by zdgeier 3mo ago
I do wonder how far you can make git work like google3. Partially why I'm making Oak is because I think it might be hard to impossible to implement the necessary features for monorepos to work correctly in Git. I don't doubt that
13.
by zdgeier 3mo ago
> Why would an agent (without fine tuning or oak-specific context) be faster with oak than it is with git or jj? A large part comes from mounts. Being able to use FSKit/FUSE to make a change to a repo rather than doing a partial&#x2
14.
by zdgeier 3mo ago
"download everything" means that you don't have to do a full or partial clone of the repo to make a change. You can imagine agents running in the cloud need to spin up and access the repo for every task, this can be slow for
15.
by zdgeier 3mo ago
Could probably build a Git backend at some point for people to use kind of like how jj does it. Right now my goal with this is to see what's possible natively if we don't try to build on top of Git. But definitely agree that the w
16.
by zdgeier 3mo ago
Great point, the readme for this repo is not great right now and we have a bunch to improve on that people have pointed out. Thanks!
17.
by zdgeier 3mo ago
Actually this https://news.ycombinator.com/item?id=34439461 contains some great discussion about JamHub if people are curious. I changed the name from jamsync to jamhub. :) Partially why I got so excited about version contr
18.
by zdgeier 3mo ago
Definitely agree and great points. This is going to be a very busy space in the next year. haha I've never used ClearCase but my friend told me about mounting VOBs in ClearCase so I'm excited it bring it back. Thanks for your thou
19.
by zdgeier 3mo ago
Agree we should definitely support offline flow. You can download the binary manually if you would like [1]. Although the offline/self-hosted flow isn't fully tested right now, would love some feedback on it if you're able to
20.
by zdgeier 3mo ago
Totally agree with everything. Definitely will be hard to get people to switch. Also love the monorepo idea you mentioned. It should totally be possible to keep the benefits of a monorepo without the downsides of git submodules. So you shou
21.
by zdgeier 3mo ago
I think what makes FUSE/FSKit great here is that agents usually only need to see the file metadata + read a handful of actual files, rather than some applications needing read many things. If you're doing huge rewrites, this is a
22.
by zdgeier 3mo ago
I love jj! Martin is really awesome and love his work. I know they're using a VFS backing inside Google for their monorepo, wonder if we'll get some of those cool features on the outside.
23.
by zdgeier 3mo ago
Thank you! The bet we're making is that agents will need to work on tasks much faster and with more parallelism than humans do with Git right now so these performance metrics will matter more. Git is awesome for human work so I'm
24.
by zdgeier 3mo ago
I'm also secretly a massive fan of Dr. Hipp and his work on FossilSCM [1]. I love a bunch of his design decisions there and wanted to apply them to a new system. [1] https://fossil-scm.org
25.
by zdgeier 3mo ago
Haha I wish, but I've been working on VCS's separate from git for a while now. Although I do love git, I've wondered for years before agents if something could be made using something different, rather than building something
26.
by zdgeier 3mo ago
Yes Lore looks awesome! I was previously working on a VCS for gamedevs -- that space definitely needs something better than Perforce haha. My comment would be that I think you need to nail a new GitHub + Git to really be successful in the s
27.
by zdgeier 3mo ago
Sick, looks great!
28.
by zdgeier 3mo ago
Awesome, thanks! You could also change it to the homepage if you'd think that would work better for people. https://oak.space
29.
by zdgeier 3mo ago
Looks awesome!
30.
by zdgeier 3mo ago
Totally agree. This is going to be the hardest dev tool to get people to switch, but we're trying! I think there's going to be many more players in this space in the next year or so. It'll be interesting to see what shakes ou

More ›