HNHacker News
TopNewBestAskShowJobs

zdgeier

662 karma · joined July 28, 2019

Contact: zach@oak.space
submissionscomments
zdgeier··on Show HN: Oak – Git replacement designed for agents
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 out.
zdgeier··on Show HN: Oak – Git alternative designed for agents
I'm a little confused by this but I assume you're talking about marking files for LFS (.gitattributes)? For us, we chunk every file (even if it's a single chunk) so every file is stored in the same way -- it's just data to us. But let me know if I got your question wrong.
zdgeier··on Show HN: Oak – Git replacement designed for agents
Check out the homepage! https://oak.space might have what you're looking for. I can answer any questions you have here as well.
zdgeier··on Show HN: Oak – Git replacement designed for agents
Planning on some monorepo features soon that should solve some submodule problems but haven't approached yet. I have some new ideas here. And yes, no separate LFS system!
zdgeier··on Your Mac has a fast, offline LLM
Woah that's cool! Was looking around something like this
zdgeier··on Show HN: Gogit – Just enough Git (in Go) to push itself to GitHub
Nice work!
zdgeier··on Meta developer tools: Working at scale
If anyone is interested in an open source VCS that's trying to solve similar problems to these internal tools check out https://jamhub.dev.

(I am the author)

zdgeier··on Let's make sure GitHub doesn't become the only option
Check out https://jamsync.dev if you're interested a non-git alternative
zdgeier··on Show HN: Jamsync – A version control system based on rsync
Hi! I’ve been working on a new version control system for the past couple months and would like to know what you think.

Jamsync aims to enable software engineers to deploy code in realtime and solve the scaling and UX problems that developers in large companies run into. It's still early in development but functions mostly as a fast file backup and syncing tool currently.

Let me know if you have any questions!

zdgeier··on Show HN: A version control system based on rsync
Yeah I agree that live editing is probably a more appropriate name right now but I think there are so many tools that already do that right now and haven't really made much impact. I don't see a large value in the live editing aspect when it comes to developing and deploying faster, even though this system will support it. The live editing is most valuable when preventing merge conflicts and working on several machines. Definitely open to your thoughts though.
zdgeier··on Show HN: A version control system based on rsync
Thanks for this!

1) Agreed, caching might not be great for large files. I don't think this is the only way though. I think there is another approach, that I haven't explored, which is storing a pointer to the last known Data block in each Range block. This means that you can just jump directly to the actual data without having to go through this regeneration or caching process. The space cost of this would be pretty low, one int per block, but it would mean that you wouldn't need to iterate through every change. Still figuring this out though and caching would be the best option if this doesn't work.

2) Yes I haven't totally figured this out yet. I'll give this a look, thanks!

zdgeier··on Show HN: A version control system based on rsync
This could work for the pulling side but really what jamsync does is both pull and push. Having changes that are always present in the remote means that merge conflicts are less likely. If you were to do this with Git, you would also have to automate the git add, commit, and push steps which would ruin the log in addition to being pretty slow.
zdgeier··on Show HN: A version control system based on rsync
Not currently, but it would definitely be interesting to have an unzip done automatically based on the file type. Then you would be able to track the contents efficiently, rather than having large binary blobs with large diffs. I haven't heard of other version control systems out there doing this.
zdgeier··on Show HN: A version control system based on rsync
There are some similarities but Fossil still has a push/pull/commit flow, although it does provide syncing features to automatically pull commits. Also, I don't think it has great support for large files.

Ultimately, the priorities of Fossil are going to be different than Jamsync, since Jamsync is not decentralized. Being centralized means that we'll be able to do some different things, like live file editing, but with some downsides related to replication and distribution.

zdgeier··on Show HN: A version control system based on rsync
More details about the problems I'm trying to solve are on the homepage if you're curious.
zdgeier··on Show HN: A version control system based on rsync
Haha appreciate you taking a look. One use case is to prevent merge conflicts, especially when working on a fast-moving project. Merge conflicts generally occur when you make changes on some old code. Jamsync constantly "rebases" your changes on top of new changes so that your code will always be up to date. Obviously some merge conflicts will still occur but much less so in this approach.
zdgeier··on Show HN: A version control system based on rsync
Yeah definitely found myself having some of the same pain points when working on multiple machines. I'll keep this in mind!
zdgeier··on Show HN: A version control system based on rsync
Thanks :) I unfortunately can't take the credit for this beautiful theme. Credit goes to https://radoslawkoziel.pl/ who made https://github.com/panr/hugo-theme-terminal which I based this off of.
zdgeier··on Show HN: A version control system based on rsync
Thanks for the feedback! What about a version control system would be valuable for storing your documents? I'm curious why you couldn't use something like Google Drive/Dropbox.
zdgeier··on Show HN: A version control system based on rsync
Appreciate the feedback! Will keep this use case in mind, this could definitely work as a layer on top of Git when people need to pair program or preview code.
zdgeier··on Show HN: A version control system based on rsync
Appreciate the feedback! I used the same name for that project but this is actually a completely different project rewritten from scratch and open-source. I've been working on the general idea for a better VCS for some time so I've restarted around 6 times so far to get something that works. Not sure it will be too productive to continue the conversation here but feel free to reach out to me if you would like.
zdgeier··on Show HN: A version control system based on rsync
Yeah this project is still pretty early in development. The main algorithm described on the site is implemented but there's a lot missing that developers would expect from a system like this. Trying to make a version control system and hosting platform in my free time while working a full-time job is not exactly an easy task haha. I plan on adding more features in the next few months.
zdgeier··on Show HN: A version control system based on rsync
This is still in-development but my plan is to essentially have "branches" which are merged and create a single "commit" on the main branch. You'll have the option to add information to a branch and a merge message if you would like, but it won't be required. I don't have any approaches on rewriting/cleaning up history right now since I think managing code history is pretty low-value for most teams. In my experience, it's far better to add another commit than it is to try to change history. Would be curious to know your thoughts though!
zdgeier··on Show HN: A version control system based on rsync
Took a look and this is really cool. Will definitely keep this is mind. One major difference and area I'm focused on in this project is hosting. I would argue that there are currently much better VCS options for projects than Git (like yours and Fossil) but the reason these haven't taken off is that Github and Gitlab offer unmatched hosting and collaboration tools for these projects. Would be curious to know your thoughts/approach to this!
zdgeier··on Show HN: A version control system based on rsync
Hi! This is the first time I'm posting publicly about this in-development project so thanks for the feedback.

Causing a conflict will cause a .jamdiff file to be written out on the next sync with the remote changes and I'm planning on adding branches in the next update which will make how this works more clear. There's still a concept of parallel editing, since features cannot be developed/tested simultaneously without breaking. Also, anytime there's a conflict, we can just make a new branch and ask the developer to merge or keep working on the new branch.

The client will watch your file system for changes and hold a gRPC stream open for remote changes. If you don't want to sync your changes, you don't have to leave the command running. CI/CD support will come later.

I'll be compliant with regulations soon, but I'm not really expecting people to use this yet. I mostly wanted to release the source and see what people thought of the project. I am using GDPR compliant Plausible analytics if that makes you feel better!

Thanks for the suggestion on the source, the zip file is up-to-date and is part of my build process. I might host on Github in the future but really wanted to make this the source of truth. My goal of open-sourcing is not to get contributors, but to give back to people who want to view the code and self host.

As far as scaling issues go, I'm planning on using an approach similar to https://madebyevan.com/algos/log-spaced-snapshots/ but I'm still figuring out the best way to handle commits.

zdgeier··on Show HN: A version control system based on rsync
Yes, that's one way to think about it. You could probably say it's closer to Google Drive than a VCS right now but my idea is to make a VCS that's more collaborative than the options currently available. Some people will have no issues with the current VCS that we have now but many developers that I've talked to have expressed frustration with the general user experience of VCSs and when merge conflicts occur.
zdgeier··on Show HN: A version control system based on rsync
The rsync paper https://www.andrew.cmu.edu/course/15-749/READINGS/required/c... is better than me at explaining this, but the rolling hash is the key to solving this misalignment problem that you describe. Essentially, using the rolling hash enables you to detect when a block as been misaligned (bytes added at the beginning of the file for example). There's no way to cause expensive resyncs in this case since it rolls over every byte in the file and reuses blocks on any alignment, even with data inserted in between.
zdgeier··on Show HN: A version control system based on rsync
Thanks! Yeah planning on adding the ability to mount specific directories so people don't have to pull down large assets they don't need, for example in gamedev or machine learning applications.
zdgeier··on Show HN: A version control system based on rsync
I'm still figuring out semantics, but currently a "commit" is made every time you make a change to a file which is synced to the remote. Every time you run `jam`, you push a commit. Or if you leave `jam` running, commits will be made each time you save. 3-way merging will be possible in the future, but will be a little different than most VCS since there is no history stored locally.
zdgeier··on Show HN: A version control system based on rsync
Thanks!
← PreviousPage 2 of 3Next →