4 ms·
Personally, I’m mostly fine with Git. But I started off with MPW Projector[0], so it's all sunshine, after that... The “UX” doesn’t bother me, as it’s a fairl
by ChrisMarshallNY 4y ago
Personally, I’m mostly fine with Git.
But I started off with MPW Projector[0], so it's all sunshine, after that...
The “UX” doesn’t bother me, as it’s a fairly classic CLI application. Any “UI” is provided by apps that are written over the CLI. That’s a common pattern in development.
I use SourceTree, for the most part, with occasional drops into CLI, for specialized tasks.
Not perfect, but adequate. I do not use the Git integration in Xcode. I find it to be inconsistent and buggy (like many Xcode features).
I have found that submodules are all but worthless, which sucks, because I feel that they really are the best way to tag aggregate codebases. From what I understand, this is because of the author’s workflow. If submodules worked like package managers, that would be wonderful.
In my experience, I find sparse checkouts to be a bit “kludgy.” I find it annoying to have to check out an entire repo, for a single file (my testing code usually dwarfs the implementation code, in my packages).
Perforce used to be good at specifying “only what is needed” workspaces.
One aspect of VSS (dating myself —no one else will) that was very cool, was the ability to specify “artificial” workspaces.
You could create a workspace that aliased files from multiple workspaces into a new aggregate. When you modified and checked in work, it could be doled out to several different repos.
That’s pretty hairy. It would be difficult to implement safely.
Git has changed the way I work. As time has gone on, I have moved away from using feature and release branches, to using tags on a single mainline.
I think forks and PRs are great things, but they aren’t actually native Git features.
[0] http://preserve.mactech.com/articles/mactech/Vol.14/14.06/VersionControlAndTheDeveloper/index.html http://preserve.mactech.com/articles/mactech/Vol.14/14.06/Ve...