Hacker News new | past | comments | ask | show | jobs | submit login

Could you be more specific?



- it's more difficult to do "agile", churning out lots of code, working simultaneously on the same pages, or functions between different teams, which then needs to be merged together by some unfortunate (possibly clueless) dev. it puts a restraint on ignorant management who don't appreciate downstream issues.

- merging and branch maintenance is more rigid with svn, so teams tend to have dedicated release teams to handles this, instead of offloading this onto devs - most devs now are expected to handle git merging and so on, not so with svn.

i worked about 10 years with svn, and 5 with git, and just my exp only of course.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: