4 ms·
>you're trying to foist a position on me that isn't mine I just said you can't give specifics on what to change, because there isn't much too change. >And you
by kadenshep 9y ago
>you're trying to foist a position on me that isn't mine
I just said you can't give specifics on what to change, because there isn't much too change.
>And you act as if source control were invented with Git
No I'm not?
>and we're left with a far, far worse industry standard.
Yeah, we definitely should have gone with the system that can't do partial checkouts correctly or even roll things back. Branching name conflicts across remote repositories and bookmark fun! Git won for a reason, because it's good and sane at what it does.
- pjmlp 9y agoThat reason was called Linus and Linux kernel development. The master can do no wrong.
- AstralStorm 9y agoNo, the reason is mercurial sucked at performance with many commits at the time, and was extra slow when merging. Lacked a few dubious features such as merging multiple branches at the same time too. It has improved but git is still noticeably more efficient with large repositories. (Almost straight comparison is any operation on Firefox repository vs its git port.)
- pjmlp 9y agoMercurial has always been better than Git on Windows. Those dubious features are so relevant to daily work that I didn't even knew they existed.
- AstralStorm 9y agoGit main target is Linux. Obviously. Performance on the truly secondary platform was not relevant and it is mostly caused by slow lstat call. Instead Mercurial uses additional cache file which instead is slower on Linux with big repos. But happens to be faster in Windows. And the octopus merge is used by kernel maintainers sometimes if not quite a lot. That feature is impossible to add in Mercurial as it does not allow more than two commit parents.
- pjmlp 9y agoWhich reinforces the position that git should have stayed a Linux kernel specific DVCS, as the Bitkeeper replacement it is, instead of forcing its use cases on the rest of us.
- kadenshep 9y ago>Which reinforces the position that git should have stayed a Linux kernel specific DVCS No it doesn't? People use octopus merges all the time, every single day.
- pjmlp 9y agoWell, I only get blank stares when I mention octopus merges around here.
- btschaegg 9y ago...as I get stares (okay, mostly of fear) if I point out that we need a branch in my workplace. What you can/can't do (sanely) with your tool shapes how you think about its problem space. To emphasize that even more: Try to explain the concept of an ML-style sum type (i.e. a discriminated union in F#) to someone who only knows languages with C++-based type systems. You'll have a hard time to even explain why this is a good idea, because they will try to map it to the features they know (i.e. enums and/or inheritance hierarchies), and fail to get the upsides.