zdgeier

9 ms·

61.
by zdgeier 3y ago
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)
62.
Show HN: Open-source version control for game developers(github.com)
1 points by zdgeier 3y ago|0 comments
63.
Show HN: CDC-Based Version Control(github.com)
1 points by zdgeier 3y ago|0 comments
64.
Show HN: Open-source version control for game development(github.com)
1 points by zdgeier 3y ago|0 comments
65.
Forth Generation Version Control(jamsync.dev)
2 points by zdgeier 3y ago|1 comments
66.
by zdgeier 3y ago
Check out https://jamsync.dev if you're interested a non-git alternative
67.
by zdgeier 3y ago
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 develope
68.
Show HN: Jamsync – A version control system based on rsync(jamsync.dev)
1 points by zdgeier 3y ago|1 comments
69.
by zdgeier 4y ago
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 asp
70.
by zdgeier 4y ago
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
71.
by zdgeier 4y ago
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 t
72.
by zdgeier 4y ago
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&#x27
73.
by zdgeier 4y ago
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 prio
74.
by zdgeier 4y ago
More details about the problems I'm trying to solve are on the homepage if you're curious.
75.
by zdgeier 4y ago
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"
76.
by zdgeier 4y ago
Yeah definitely found myself having some of the same pain points when working on multiple machines. I'll keep this in mind!
77.
by zdgeier 4y ago
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.
78.
by zdgeier 4y ago
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.
79.
by zdgeier 4y ago
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.
80.
by zdgeier 4y ago
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'v
81.
by zdgeier 4y ago
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
82.
by zdgeier 4y ago
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
83.
by zdgeier 4y ago
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
84.
by zdgeier 4y ago
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 plannin
85.
by zdgeier 4y ago
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
86.
by zdgeier 4y ago
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 describ
87.
by zdgeier 4y ago
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.
88.
by zdgeier 4y ago
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 wil
89.
by zdgeier 4y ago
Thanks!
90.
by zdgeier 4y ago
Ah awesome! I'll check this out

More ›