[flagged]
Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
61–70 of 440 posts
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#62Earlier quoted context omitted.
Even a force push doesn't destroy the reflog or runs the GC server-side. I wonder how you can accidentally loose data with Git. I've seen lot's of people not being able to find it, but really destroying it is hard.
He force pushed a diverged branch or something like that, and we only found out after a while. We were eventually able to recover because someone didn't pull. But it was not a fun experience :D
So you were able to recover and did not lost a months work of data? Your story just doesn’t make sense. Come on.
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#63Earlier quoted context omitted.
He force pushed a diverged branch or something like that, and we only found out after a while. We were eventually able to recover because someone didn't pull. But it was not a fun experience :D
So the work wasn’t actually destroyed, and you were able to recover it. So all the people pointing out how implausible that part of your pitch was were right, and you were in fact just lying.
That's really not the main point of the post, but you're right I should have been more precise.
Edit: updated in the top text now!
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#64It's about time someone revisited & reimagined version control. the previous generations each lasted about 15 years: SCCS/RCS -> CVS -> Bitbucket/git/mercurial -> ??? so I am glad to see this. I would start by talking about what is great about Diversion -- what it lets you do that you couldn't before. Since you mention gaming and perforce I looked in vain to see if it supports binaries (a major limitation of git -- j…
??? might be https://pijul.org/ with its commutative awesomeness
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#65Congrats on the HN launch. How does this improve or expand or blow git-lfs[1] out of the water because if I needed large blob file support it's what I would use instead. It offers pointers to the big files to the hosted git instead of pushing around the binaries itself -- though I am speculating since I've not used it myself just read about it online. I mean the nice UI and collab features are indeed improvements but…
Git LFS solves the problem if you need to have occasional large files in your repo. It doesn't work great though when you have a lot of them or when they're an integral part of your product, because it's slow and introduces devops problems (e.g. you can bomb your repo by committing from a clone without Git LFS installed). Companies that have many large files to manage rarely use it because of this.
Okay. That’s fair and info I didn’t have.
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#66Nice. I make music and use git for my files, but often hit the usual space limitations and I hate dealing with git-lfs. I think there's a big use case for Diversion and music/video production.
I assume the space limit your are talking about is rather a Github/Gitlab/Bitbucket limit. May I ask, how you use Git for your music? Since binary diffs are not really a thing, the main benefit I could imagine is simply having revisions of your files with you having to create folders or having files named "track01_test_final2.flac"
I literally just `git add .` and let her rip. It's not pretty, I just git pretty much everything in my life.
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#67You are not competing with Git, you are competing with Perforce.
(Personally, I would never use a proprietary cloud-only offering for version control.)
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#68Focusing on Git seems like completely the wrong pitch. Git is a distributed VCS - in all your examples you were clearly trying to use Git in a centralized manner with no backups. I suggest focusing more on your own product than on Git.
You're totally right, we were using BitBucket and pushing and pulling from there. It's really more of a centralized manner, but this is the usual workflow for most teams and companies and what they actually need (a single source of truth). Totally agree about backups, lesson learned :)
I want to add counter-feedback. I think focusing on git's weaknesses is really appealing. My background is more ML research and data and I viscerally connect with your pitch around both git's limited scalability and the complex/dangerous nature of git operations (ML researchers + git is not great).
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#69Being deceptive about Git's shortcomings is going to raise eyebrows with anyone seriously evaluating your solution, which is already going to raise eyebrows because it's not free software. Most studios will try to avoid locking themselves into another expensive, annoying VCS that they have no control over. There's good attempts at FOSS p4 replacements now, you need to do better if you want to stand out.
> There's good attempts at FOSS p4 replacements now, you need to do better if you want to stand out.
There are? Like what?
Re: Launch HN: Diversion (YC S22) – Cloud-Native Git Alternative
#70Your core feature is live updates of changes. That is actually a nightmare. I don't want live updates. It will be a mess.
If you really want to do cloud. Use git.