Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Some of the many reasons:</p> <ul> <li><p>Inertia: There's an enormous number of people out there familiar with centralized systems. You don't have to "retrain" developers if you just don't change.</p></li> <li><p>Interactions with other tools: Corporate environments are of course big on extra tools like continuous integration, IDEs, fancy issue trackers, and so on. Naturally, there's more support for the established centralized VCSs with those than with the relatively new git and hg.</p></li> <li><p>Support: When you buy a commercial VCS product, you're not just buying the program, you're buying peace of mind.</p></li> </ul> <p>Of course, I'm not saying these are <em>good</em> reasons; they're just convincing to people in the position to make this decision. I think it's worth overcoming inertia - it takes work now, but it pays off later. I think the external tools are getting better at supporting git, particularly the open-source ones - they just need plugins. And as for support, we all know there's plenty of less formal support out there on the internet.</p> <p>Really, there's a common thought in all of these - the free software philosophy just isn't the way corporations do business. Buying a product is established and easy. You pay your money, you get what you need. Management doesn't have to worry. Using a free software product... well, it may be much better, but it's more complex to deal with. It doesn't come in a box.</p> <p>A clarification: I use the word "free" in the same way those in the free software world do - free as in freedom not as in beer. Hopefully this phrase will get drilled into everyone's heads eventually. Note that I never dealt with the issue of cost here - though I do think that in the case of git, in general it will be ultimately be cheaper than a purchased solution despite the costs of bringing everyone up to speed on it and making sure it fits in with the rest of your process. This isn't a cut-and-dry issue though, and since I think git comes out ahead, there's no sense putting it among the bullets.</p>
    singulars
    1. This table or related slice is empty.
    1. POReasons against using "Git" in the enterprise
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCascabel
    1. USCascabel
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COFree software isn't always *free* in the enterprise world (with emphasis on your first two bullet points -- those cost money in the enterprise world). Even the cost of support can be offset with possibly having to hire another employee dedicated to the tasks the support contract would have provided. Though I do agree with you that they aren't *good* reasons for using an inferior tool.
      singulars
      1. PO
      1. USAustin Salonen
    2. COAlthough the professional costs of psychiatric care for devs forced to use VSS and the security guards for when they go postal are also rather high.
      singulars
      1. PO
      1. USMartin Beckett
    3. CO@Austin Salonen: edited in a response to your comment.
      singulars
      1. PO
      1. USCascabel
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload