#ComparingPlasticAndGit
nocturne fog
They used it at the company that I'm working for when I joined. You don't want to change version control mid-project. And Plastic does have a few things that I really like: The way it manages branches, merging and cherry-picking is just really awesome.
The two really big things that I miss are sparse checkout (that's what Plastic pretends to have and they even have a really arrogant and incredibly ridiculous blog posting about it).
And partial commits: Not sure if that's a Git feature or rather a GitHub Desktop feature - but in GitHub Desktop you can decide for each line in a file which ones you want to commit with the current commit, and which not, so you can spread changes over several commits which can be quite useful if you've done too much work that wasn't really related in a single session. Plastic at least lets you undo changes per-line, so you can kind of work around not having that feature by making a copy of the file, then undoing changes you want for the next commit, commit, copy over the file ... it kind of works but it's a major hassle compared to the workflow in GitHub Desktop which is just elegant.
Managing large feels worked fine for me on both (using Git LFS). But I have only used Git in very small teams (mostly myself, sporadically a few more people) and by now have spent years using Plastic in a larger team.
Managing large files feels ... lol also
feels😉
willow stratus
Even changing version control between projects will be a big change to the company!
I don't know what sparse checkouts are, unless I'm using them without knowing?
Partial commits aren't a GHD feature. I use Git Fork and can do it (commit or discard).. very useful, like you say
Sounds like it's a good/decent versioning system, with its own pain points