3 ms·
> Have you ever wanted to store your version controlled repositories inside a Dropbox folder? Or continuously backup repositories to S3? No? Well, now you can!
by benrutter 2y ago
> Have you ever wanted to store your version controlled repositories inside a Dropbox folder? Or continuously backup repositories to S3? No? Well, now you can!
This made me chuckle. In all seriousness, does jj afford anything new by connecting to filesystems more directly?
The main issue with git I've heard of is for projects, like video games for instance, that bundle text based code with a huge amount of non-text assets (audio, images etc).
I don't understand what causes gitissues here, is it storage? Or is it more attempting to map differences between non-text assets. Curious about whether jj's filesystem usage help here.
- steveklabnik 2y agoThat claim has nothing to do with integrating with file systems. Issues with Dropbox and git are fairly well known https://stackoverflow.com/questions/19305033/why-is-putting-git-repositories-inside-of-a-dropbox-folder-not-recommended https://stackoverflow.com/questions/19305033/why-is-putting-... Jj interacts with files in a way that ensures this can’t happen. Jj is the same as git with regards to large non-text assets. But that’s just because it’s still young, it will gain good support eventually. (And yeah it’s about storage and also about diffs. How would you fix a merge conflict in a PNG?)