3 ms·
don't fix what ain't broken? i think as long as git keeps evolving and there are no major pitfalls for any programming language: why should it be replaced?
by wickedOne 6y ago
don't fix what ain't broken?
i think as long as git keeps evolving and there are no major pitfalls for any programming language: why should it be replaced?
- rurban 6y agoBecause it is broken. Merges and rebases rarely work without manual intervention, a patch-oriented tool that is almost as fast as a snapshot-oriented tool, git. Something like Pijul looks promising.
- pskinner 6y agoIt doesn't work because your changes conflict? How would anything else handle out of order modifications to files that cannot be resolved automatically? There will always been a requirement to do this manually - otherwise the VCS would be able to program for you (understand what is right/wrong).