3 ms·
> Other than the 2nd-to-last point (slow binary mod detect), performance wasn't otherwise listed in the README, so I don't know why you're calling me out for om
by sebastian_io 6y ago
> Other than the 2nd-to-last point (slow binary mod detect), performance wasn't otherwise listed in the README, so I don't know why you're calling me out for omitting it.
The ones I was referring to for performance are:
- Support for instant snapshots
- Support for instant rollback
About alternatives, Perforce and PlasticSCM are currently commonly used. But I understand your objections, and will check if I can handle certain things differently in the README. Thanks again for your input!
- lucideer 6y agoThanks, and apologies it if came across overly critical. I just think things like this can be impactful to perceptions of the work done on efforts such as Git-LFS, and describing things based on their own merits is often a better approach than pointing out lack elsewhere. A VCS UI for design is something I've been looking for for a LONG time, so I signed up to the SnowTrack public beta immediately. I was just a little confused/concerned to learn it won't have a widely-supported backend to ease things such as synchronisation across devices, sharing resources via a hosted service, etc. Curious to see how this gets handled in the final product.
- sebastian_io 6y agoI really appreciate your critical view on the project, because it makes me reflect my own stand and arguments and to see if they are correct or wrong. E.g. I just removed the "without LFS" argument because you are right, this is not a sustainable argument and I will address a few more soon to clear things up. I learned a lot during the development of SnowFS and the open-source-community is the best place to share my experiences, that's why I put it on GitHub. At the end, I would be super happy if these insights can make it over to Git and Git-LFS. We have a Discord channel, you are very welcome to swing by anytime for a virtual beer :-)