git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Git User's Survey 2008 partial summary, part 5 - other SCM

From
Ddavid@lang.hm <david@lang.hm>
Date
Sep 11, 2008, 22:51 UTC
Message-ID
<alpine.DEB.1.10.0809111543580.15169@asgard.lang.hm>
In-Reply-To
<200809112214.18366.jnareb@gmail.com>
On Thu, 11 Sep 2008, Jakub Narebski wrote:
Show 8 quoted lines
> A bit suprising for me is high place of Perforce.  Another strange
> thing (and a bit alarming) is that MS Visual SourceSafe has higher
> place than Monotone; but that might be caused by different design and
> different target groups of Monotone and Git, which might have caused
> that the communities have almost no overlap; people choose either Git
> or Monotone, one or the other.  BitKeeper has also a very low number
> of active users among Git users... but that is not that strange,
> considering history.
I think you are making the wrong assumption here.

someone may use CVS becouse they contribute to a project that is only availabe via CVS

someone may use Perforce becouse that is the VCS that their company uses

if you do commercial development with windows you are almsot going to be required to use MS VSS.

you are looking at it from the point of view of 'which VCS would you select for a new project', but that would be a very different question.

I find it interesting that the number of people who use git and the other DVCS systems in so small. Is this becouse the 'market share' of those other systems is small? or becouse people who learn git aren't willing to put up with other systems (or vice-versa)? or is there some other trend or tendancy that makes people who select one DVCS more likely to work on similar projects, so people interested in those types of projects will generally just see a single DVCS system

David Lang
Previous: Jeff KingNext: Jakub Narebski
Message 23 of 33 in “Git User's Survey 2008 partial summary”
  1. Jakub NarebskiSep 3, 2008
  2. Shawn O. PearceSep 3, 2008
  3. H.Merijn BrandSep 3, 2008
  4. Felipe ContrerasSep 3, 2008
  5. David AguilarSep 4, 2008
  6. Jan HudecSep 5, 2008
  7. David AguilarSep 6, 2008
  8. David BrownSep 3, 2008
  9. Scott ChaconSep 3, 2008
  10. Jakub NarebskiSep 3, 2008
  11. Jakub NarebskiSep 4, 2008
  12. Git User's Survey 2008 partial summary, part 3Jakub Narebski, Sep 6, 2008
  13. Shawn O. PearceSep 6, 2008
  14. Andreas EricssonSep 6, 2008
  15. Jonas FonsecaSep 7, 2008
  16. Shawn O. PearceSep 7, 2008
  17. Git User's Survey 2008 partial summary, part 4 - how do we use GitJakub Narebski, Sep 6, 2008
  18. Andreas EricssonSep 7, 2008
  19. Jakub NarebskiSep 7, 2008
  20. Git User's Survey 2008 partial summary, part 5 - other SCMJakub Narebski, Sep 11, 2008
  21. Anatol PomozovSep 11, 2008
  22. Jeff KingSep 11, 2008
  23. david@lang.hmSep 11, 2008
  24. Jakub NarebskiSep 12, 2008
  25. david@lang.hmSep 13, 2008
  26. Jakub NarebskiSep 13, 2008
  27. Mark BrownSep 15, 2008
  28. Nguyen Thai Ngoc DuySep 14, 2008
  29. Jakub NarebskiSep 14, 2008
  30. david@lang.hmSep 15, 2008
  31. Andreas EricssonSep 15, 2008
  32. Jakub NarebskiSep 16, 2008
  33. Jakub NarebskiSep 11, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.