4 ms·
As someone who was there in the very very early Subversion meetings, I'm surprised it took this long for them to migrate.
by latchkey 4y ago
As someone who was there in the very very early Subversion meetings, I'm surprised it took this long for them to migrate.
- miohtama 4y agoWhat's a decade or two in the grand scale :)
- samstave 4y ago
- olliej 4y agoThe Git dev model is _very_ different from cvs, svn, etc so the trade offs are less obvious. A lot of the benefit of git to me has always been the local development model, but the git-svn bridge made that largely transparent which I think lowered the pressure to change.
- latchkey 4y ago> The Git dev model is _very_ different from cvs, svn, etc so the trade offs are less obvious. I think that the difference makes the tradeoffs using anything other than git, more obvious. I even held out myself for a very long time with svn vs. git and once I switched... I kicked myself for not doing so earlier. But, like they said in the post... they did need a feature, which is core to svn (incrementing changelog ids) and a workaround in git. Minor in the grand scheme of things.
- bastardoperator 4y agoIf they had floating or dynamic externals and a bunch of permission models, I'm not surprised at all. I'd label this more of a conversion versus a migration.
- xtracto 4y agoI remember migrating some codebase from CVS to SVN ... and this was sometime after CVS was adopted instead of "at the end of the day, every dev will copy his change into a floppy disk and give it to the Tech Lead for merging". This was during the 90s in a software development company in Mexico. Good times!
- hnfong 4y ago> This was during the 90s in a software development company in Mexico. Version 1.0 of svn was released around 2004. According to wikipedia the project was started around 2000. (Sidenote: there seems to be cognitive dissonance that svn was released much earlier than git ... but svn was released in 2004, and git in late 2005. There's a less than two years gap in between, yet so many projects had been "stuck" with svn...)
- ayewo 4y agoIIRC, svn was marketed as "CVS done right" [1], which meant devs who were exploring alternatives to CVS didn't have to worry about svn's learning curve. So, I think inertia may have been a huge part of why adoption of svn was so good compared to git that has a steep learning curve, even today. 1: Of course, Linus Torvalds believes you can never do CVS right https://www.youtube.com/watch?v=4XpnKHJAok8 https://www.youtube.com/watch?v=4XpnKHJAok8 and there's a transcript: https://gist.github.com/dukeofgaming/2150263 https://gist.github.com/dukeofgaming/2150263
- ReptileMan 4y agoUnpopular opinion - git is just not that good of a source control tool. Amazing as a distributed system, but mediocre in its primary function.
- antris 4y agoSource control is an inherently distributed system. Each developer has their own copy of the code that are distributed across many computers, and they need to communicate between each other. That's exactly what the primary function of the software is.