3 ms·
"SVN vs Git" An excellent comparative case in point that in my opinion actually undercuts what you are asserting. You do not lose features and functionality i
by lucifer 17y ago
"SVN vs Git"
An excellent comparative case in point that in my opinion actually undercuts what you are asserting.
You do not lose features and functionality in that transition (where as noSQL is by design reductive), and further, Git is a replacement for SVN and not a complementary tool.
- bphogan 17y agoActually you do lose functionality by going that way. SVN handles binaries better. I can also cherry-pick files from a directory structure, so if I need to fetch out a subfolder or an individual file, I can do so. With Git I must clone the repo or set up a web service so I can get access to the file system. But they're different tools for different audiences. In my environment, I do use both of these tools together. The lesson Git, Ruby, Subversion, Apache, and many other projects have taught me is that instead of saying "What I have is fine, I don't need what you have", I need to ask "Why do you use what you use, why does it help you, and how might it help me?