6 ms·
git has more or less completly taken over the mindshare from all other version control system.
by belorn 11y ago
git has more or less completly taken over the mindshare from all other version control system.
- nailer 11y agoI think sometimes we forget that network effects outweigh most normal values of technical superiority. Let's say, for the purposes of the argument, that "hg/Mercurial is 20% better than git". This doesn't matter: hg/Mercurial has to be 500% better than git to be able to replace it. Look at the past changes: they've all been huge shifts in how we do version control, not minor improvements The DVCSs were 500% better than Subversion (wow, distributed!) Subversion was 500% better than CVS (wow, renames work! Branching is easy! http support!) CVS was 500% better than RCS (wow, we can check out files concurrently)
- octo_t 11y ago> Branching is easy when svn first came out (and up until a few years ago) branching was definitely not easy!
- lfowles 11y agoWhat changed a few years ago?
- anonydsfsfs 11y agoSubversion 1.5 added support for tracking merges: https://subversion.apache.org/docs/release-notes/1.5.html#merge-tracking https://subversion.apache.org/docs/release-notes/1.5.html#me... Before this, merging branches was a huge pain, because you had to manually keep track of the commits that needed to be merged.
- threeseed 11y agoYou are right. But it is often referred to as the 10x rule. http://www.minidisc.org/econ113-paper.htm http://www.minidisc.org/econ113-paper.htm A technology needs to be 10x better than a previous one for widespread adoption. It has successfully explained many failed technologies and products.
- kazinator 11y ago> A technology needs to be 10x better than a previous one for widespread adoption. It has successfully explained many failed technologies and products. A hypothesis about failure, on the other hand, has to account for the failures and successes. This one doesn't. While it can plausibly explain failed technologies and products, it doesn't explain the historic success of junk that is worse than its predecessors. A technology can be hyped into widespread adoption. It can be dumped on the market for widespread adoption. It can ride on top of cheap hardware for widespread adoption. It can be bundled with something else, achieving widespread adoption. A technology can be falsely evaluated as 10X better by a large number of complete idiots, resulting in widespread adoption among idiots, resulting in pressure for non-idiots to adopt. All these effects can overcome the barrier of having to be actually, objectively 10X better. The "10X better adoption barrier" is only faced by honestly promoted technologies whose campaign consists of "try this because it's better for these objective reasons".
- 0x0 11y ago"Better" can mean a lot of things including "cheaper", "easier to use", "better marketed", etc. Explains why sometimes "worse is better", I think :)
- kazinator 11y agoYes; "worse is better" rings true when the "worse" on the left hand side is the antonym of a different meaning of "better" from the right hand side "better"; i.e. an equivocation on the word is going on (not to deceive but to create a play on words).
- vezzy-fnord 11y ago(wow, distributed!) With the ultimate irony that people largely use it in a centralized fashion.
- skeeterbug 11y agoA central origin sure. It is nice knowing I can work offline which is my general workflow. I can also experiment with local branches and not push them to a remote.
- Manishearth 11y agoDo people work on the same files/folders at the same time? Then the workflow is already way more distributed than svn ever was :)
- ams6110 11y agoWe did that in svn all the time with few issues.
- kazinator 11y agoDistributed doesn't mean decentralized; they are not synonyms. DNS is distributed, yet it has a "root" servers. Even if there a master repository in a given git scenario, it is still distributed because developers have their own repositories, which are independent, and contain a replica of the copies of the upstream objects.
- vezzy-fnord 11y agoThe point is that at least for a VCS, centralization does largely subvert the distributed aspect. At that point, you no longer really have multiple repositories so much as multiple working copies, similar to a CVCS. Your work model revolves around a blatant SPOF which you must synchronize all changes to. The Linux kernel is a proper example of distributed workflow.
- kelnos 11y ago
- ionforce 11y agoIt's like the coefficient of friction. The amount of force required to move an object at rest is greater than the amount of force required to maintain it already moving (or something like that).
- kazinator 11y agoThat's not really a "network effect", but more of an "activation potential barrier". If it cost almost nothing to migrate to a new system, then 5% better might be a good enough reason. If I'm going to do back-end setup, data migration and re-train myself and others, then, damn it, I demand a 500% improvement to show for it. :)
- dredmorbius 11y agoIt's a network effect. If you're going to attract new contributors to a system, having the toolset that everyone else uses is a huge win. I've been at this long enough to have learned (somewhat) each of RCS, CVS, SVN hg, and git. In the beginning there were (mostly) just two: RCS and SCCS, and nobody used SCCS. With time, I've touched several others, had to wrap my head around them, as additional challenges to getting my primary job done, which generally involved solving problems in other domains (or learning other tool). And ... some of that's knowledge which has stuck, some isn't. The time invested in learning is sunk cost, though there's the problem that it all leaves traces on your brain. This is something that 20-somethings don't get: it's not learning things so much as unlearning. It's one thing to launch into a field with the hot new technology under your belt. I landed with some awarness of Unix when that was fairly unusual, and parlayed that and a set of tools for 25 years. During which I've not stood still... ... but the rate at which new tools are introduced, and having to sort out which actually will win is a considerable overhead. After a while it ... just gets kind of old. Especially since you realize that all of it is a constructed complexity, largely arbitrary. How many operating systems (7, not counting Unix variants), shells (9), editors (10+), scripting languages (8), database implementations (7), firewall systems (4), webservers / application engines (6), mailservers (6), document markup languages (6+), etc., etc., etc., do you want to learn over your lifetime? Some are pretty cool. Others ... are just makework. This spills over to larger highly integrated stuff which previous experience shows is almost always going to be a massive clusterfuck, of which I'll not mention systemd by name. Which means you want to consider what projects you work on, where you work, etc. Google have a challenge in this regard with their NIH model -- work at Google long enough and you'll learn some really cool, advanced technology. Which nobody, anywhere else, uses. And, no, they're not the only ones. But they definitely come to mind.
- ngoldbaum 11y agoMight changeset evolution [1] (e.g. safe collaborative rewriting of public history) be that 500% bonus? [1] https://mercurial.selenic.com/wiki/ChangesetEvolution https://mercurial.selenic.com/wiki/ChangesetEvolution
- rbehrends 11y agoChangeset evolution is conceptually brilliant [1], but I suspect that it's really something that only a few percent of VCS users will actually use (at least beyond the level of features that Mercurial and Git already support). [1] ... in that it provides not just safe mutable history, but shared mutable history.
- david-given 11y agoI use hg as a front end to git, so I get the advantages of git's mindshare without having to deal with git's UI. Now I get the best of both worlds.
- krupan 11y agoIf I ever am forced to use git I'm hoping I can do this. Does it work well? I'm being forced to use svn right now at work and hgsubversion is a little rough around the edges.
- david-given 11y agoReally well. The one stumbling block is that git branches are mapped on to hg bookmarks, and it's not quite seamless --- I haven't figured out all the subtleties yet, but it doesn't seem to get bookmark deletion right, for example (the bookmark will reappear the next time you do an hg pull). I use github as a backend, so I tend to do branch manipulation using the github UI, so this isn't an issue for me. Everything else Just Works. Highly recommended.