Slashdot Mirror

← Back to Stories (view on slashdot.org)

An Illustrated Version Control Timeline

Posted by CmdrTaco on from the remember-when dept.

rocket22 writes "Most software developers are supposed to be using the latest in tech and see themselves as living on the edge of software innovation. But, are they aware of how old some of the tools they use on a daily basis are? There are teams out there developing iPad software and checking in code inside arcane CVS repositories. Aren't we in the 21st century, the age of distributed version control? The blog post goes through some of the most important version control systems on the last three decades and while it doesn't try to come up with an extremely detailed thesis, it does a good job creating a catalog of some of the most widely spread or technologically relevant SCMs."

4 of 244 comments (clear)

  1. pardon, your ignorance is showing by rubycodez · · Score: 0, Troll

    Distributed version control systems are only useful for certain types of projects, e.g. a Linux kernel, and useless for others e.g. a three-person development team making an rpc-xml insurance claim submitter.

  2. CVS May be Old, but... by Anonymous Coward · · Score: 0, Troll

    "If it ain't broken, don't fix it."

  3. Show me an actual distributed RCS. by BitZtream · · Score: 0, Troll

    What? You really can't? You mean EVERY SINGLE ONE of what you want to call a Distributed RCS actually depends on something centralized to make it useful to anyone?

    Seriously, you guys need to get over the 'dstributed' bullshit and start realizing that anarchy and decentralization is not actually the solution to ever problem on the planet.

    There has to be some point for software to go to start looking for 'distributed' copies.

    So many people rant about which RCS to use, and 99% of you don't even know how to fully exploit even the most basic of RCS systems to their advantages.

    --
    Persistent Volume manager for Kubernetes - https://github.com/dwimsey/openshift-pvmanager
  4. Re:Arcane CVS and what not by farnsworth · · Score: 1, Troll

    But does it work for them? If so, great! Why switch to something else if you have no real need for all those features? It's not just about features, CVS is deeply broken (tagging/branching, directories, binary files, metadata, etc). Subversion is a drop-in replacement that fixes (most) of the problems and can be used in exactly the same workflow. The two are equivalent and one is less broken - it's kind of a no-brainer.

    Also, OS X ships with svn, but not cvs. I'm not sure that if you install the dev tools if that will install cvs, but I tend to doubt it.

    --

    There aint no pancake so thin it doesn't have two sides.