2 ms·
Yes. Here are areas where git sucks: * UX, obviously. * Large files (LFS is a not-very-good poorly integrated hack) * Very large projects (big company codeba
by IshKebab 3y ago
Yes. Here are areas where git sucks:
* UX, obviously.
* Large files (LFS is a not-very-good poorly integrated hack)
* Very large projects (big company codebases). Poor support for sparse/partial checkouts, stateful operations (e.g. git status still scans the whole repo every time on Linux), poor & buggy support for submodules.
* Conflict resolution. It's about as basic as it can be. E.g. even zdiff3 doesn't give you quite enough information to resolve some conflicts (you want the diff for the change that introduced the conflict). The diff algorithms are all fast but dumb. Patch based VCS systems (Darcs, Pijul) are apparently better here.
IMO the most interesting projects that are trying to solve any of these (but not all of them sadly) are Jujitsu and Pijul.
- zer00eyz 3y ago> The diff algorithms are all fast but dumb. Patch based VCS systems (Darcs, Pijul) are apparently better here. Isnt one of git's core features that it can work as a patch based system? It's my understanding (and please correct me if I'm wrong) that Linux patches can come in via mailing list, as a diff. That would make the person committing different from the owner of the change (also reflected in git's design)? Do Darcs and Pijul just have a string of patches on top of the original source file?
- IshKebab 3y agoGot can apply patches, yes. But I mean when it has two commits (which are snapshots, not patches) and it uses a diff algorithm to synthesise a patch between them. It uses an algorithm which is great from a computer science point of view (low algorithmic complexity, minimal length, etc.) but pretty bad from a semantic point of view (splitting up blocks, etc.). There are a couple of attempts to improve this (DiffSitter, Difftastic) but they don't integrate with GUIs yet.