3 ms·
At my company we use both SVN and Git (via GitHub) at the same time. SVN is for the serious dev while Git is for toy project we post online from time to time.
by passfree 13y ago
At my company we use both SVN and Git (via GitHub) at the same time. SVN is for the serious dev while Git is for toy project we post online from time to time.
Some of you may say that we may not be doing things right but the only reason SVN is preferred over Git is because of externals. It is just easier to reference an external project and keep it updated all the time. This is important for consistency point of view and we want to spend more time developing features verses merging and resolving merge conflicts, etc. When we tag things we simply svn copy and then flatten the externals making it all the same. It works great for us and we cannot see any reason why we should move away from this.
Git is interesting and definitely very powerful. We love the idea of working on a feature and then commit push and merge it when it is ready. It does make a lot of sense to do this over and over again but there is sooooooo much to type all the timeeeeee. It makes it so inconvenient.
Maybe it is just our model of work. Maybe we are weird and old school.
- fayyazkl 13y agoLoved the part regarding sooo much to type. I learned svn in probably in my first job and after a while, commands just came natural to me both linux command line or toroise svn via GUI. But git which i only learned a couple years back still haunts me in the sense of writing a long command with several parameters to achieve some thing where i have to understand each param and its application in my given scenario. Just a week back, i spent like 30 min getting code base back to the state of some one doing an equivalent of svn update and i was like... Why did we ditch svn?