By jasonslickedit
via blog.slickedit.com
Published: Sep 18 2008 / 19:58
There are an unbelievable number of version control systems out there. They all have their strengths and weaknesses, and almost everyone has a strong opinion about which one is best. These software tools weren’t written by some group of developers that were out of touch with their end users either. They are all developer tools, written by developers for developers. Many of them were born from previous version control packages, such as how SVN evolved from CVS. The purpose was to keep what was good about the previous system and redo what they felt was lacking.
-
ICEfaces 3.0 Released - New and Noteworthy
-
Phoning it in: the dirty secret of IP calling, and how it will change the phone industry
-
Sneak peek at the greatest toy robot ever invented
-
Attila Szegedi on JVM and GC Performance Tuning at Twitter
-
The story of the mysterious WINA20.386 file
-
The depths of Java: API leak exposed through covariance
Comments
sproketboy replied ago:
Fail.
wekempf replied ago:
You're correct, that comment did fail.
Seriously, not a helpful post. Why bother spending the time to write it?
There's serious problems with the idea behind this post, but it's not an entirely bad idea.
dragmire replied ago:
I like the idea, but enough version control systems are different enough in how they implement the service that it'll never be put in place. The reason we have so many is because so many groups required different functionality than what was provided.
Voters For This Link (11)
Voters Against This Link (4)