11–20 of 440 posts
Perforce seems to already fill this niche pretty well, at least in the gaming sector which this startup seems to target.
I mean the nice UI and collab features are indeed improvements but I'm thinking more core git specific improvements.
> In our previous startup, a data scientist accidentally destroyed a month’s work of his team by using the wrong Git command. While git is indeed a usability clusterbomb and there is massive space to improve, the problem above sounds like a devops failure. Git gives you all the tools to prevent such a disaster, all you have to do not give the root password of your CI server to any data scientist. On the topic of your…
You _really_ have to try to fuck up hard enough that everything is gone, it just might require even more arcane commands than what got you into a mess.
Do you have more documentation somewhere? If so, I’d suggest making it more easily accessible. I couldn’t find any on the site and the support link just takes me to discord. I’d be more inclined to sign up if there was some documentation I could read through to get a sense for requirements, setup, branching, CLI commands, etc.
>>it was built for a very different world in 2005 (slow networks, much smaller projects, no cloud)
Slow network: why is this a negative thing? If something is designed for a slow network then it should perform well in a fast network.
Mush small project: I do not agree. I can say that it was not designed for very very large projects initially. But many improvements were made later. When Micorosoft adopted Git for Windows, they faced this problem and solved it. Please look at this https://devblogs.microsoft.com/bharry/the-largest-git-repo-o...
No cloud: Again I would not agree. Git is distributed so should work perfectly for the cloud. I am not able to understand what is the issue of Git in the cloud environment.
>>In our previous startup, a data scientist accidentally destroyed a month’s work of his team by using the wrong Git command
This is mostly a configuration issue. I guess this was done by a force push command. IFAIK, you can disable force push by configuration.
Do you have more documentation somewhere? If so, I’d suggest making it more easily accessible. I couldn’t find any on the site and the support link just takes me to discord. I’d be more inclined to sign up if there was some documentation I could read through to get a sense for requirements, setup, branching, CLI commands, etc.
Congrats 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…