Timeline for Why does everyone use Git in a centralized manner?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2016 at 21:53 | comment | added | Karl Bielefeldt | Those company policies seem strange now that DVCS is ubiquitous and people are used to its perks. Before the DVCS revolution, these policies were nearly universal, and they are still very common in large organizations. | |
| Apr 13, 2016 at 19:09 | comment | added | fishinear | All disadvantages you mention are due to very strange company policies, and not inherent limitations of a CVCS. Typically you can limit which users can merge into certain branches, every developer typically works on a personal branch, where you can commit as much as you like, and anybody can typically create new branches (for example if you run two development tasks in parallel). | |
| Apr 13, 2016 at 13:09 | comment | added | Lie Ryan | @JerryOL: "uphill both ways" yeah, that's what you needed to do to get to that ivory tower. | |
| Apr 12, 2016 at 18:54 | comment | added | JerryOL | and don't forget about walking to school in the rain and snow, almost eight miles uphill both ways. | |
| Apr 12, 2016 at 12:45 | comment | added | Wayne Werner | @gardenhead apparently projects are being released at a pretty insane rate. The ability to continue learning is necessary if you want to be able to find an awesome job. | |
| Apr 12, 2016 at 4:10 | comment | added | Stack Exchange Broke The Law | @WayneWerner IIRC, sometime after Git became dominant, SVN got "svn init", and the ability to use any old shared directory as a server. | |
| Apr 11, 2016 at 18:34 | comment | added | gardenhead | @leftaroundabout Sometimes I'm jealous of them, if that is the case. I think since my year working out of college, I've had to learn about one new technology per week. | |
| Apr 11, 2016 at 15:25 | comment | added | leftaroundabout | @gardenhead: well, consider yourself lucky that you're not stuck in a legacy project, with old software developers who are telling you the old way of doing things is just fine... sometimes you can't help but feel they are just glad they don't need to learn any new technologies! | |
| Apr 11, 2016 at 0:51 | comment | added | Wayne Werner | @gardenhead you can always create your own SVN repo and try to break it ;) (and notice how much harder it is than creating a git repo and cloning it...) - One other major feature I've noticed (at least in corporate environments especially) is that file sharing is either a bit awkward, or it's done in such a way that horks up repositories (because virus scanner locks on a network drive, for instance). | |
| Apr 10, 2016 at 16:31 | comment | added | gardenhead | You're right, I don't know how easy I have it. I wish I had been around in the days of SVN dominance to appreciate how far we've come. As a very young software developer, I find this same pattern repeating quite often: the more experienced devs telling me that the old way of doing something was bad, and this new way / technology is much easier. But I just have to take their word for it; I can never truly appreciate the advantages. I've always found this dissonance difficult to overcome. | |
| Apr 10, 2016 at 7:06 | comment | added | cmaster - reinstate monica | The question how hard it is to create a branch in a traditional CVCS is entirely down to policy: I happen to work with an upstream SVN repo (naturally via a git-svn clone!), and I have every right to create any branches I want to, even though it's quite a large project. I'm just not allowed to touch a number of designated integration branches, let alone the trunk, without talking to my superiors first. Other companies may have other policies which may be more restrictive, but they certainly don't have to be. | |
| Apr 10, 2016 at 5:43 | history | edited | Karl Bielefeldt | CC BY-SA 3.0 | address OP's edit |
| Apr 9, 2016 at 21:40 | history | answered | Karl Bielefeldt | CC BY-SA 3.0 |