git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverre Rabbelier" <alturin@gmail.com>
To: "Daniel Barkalow" <barkalow@iabervon.org>
Cc: "Teemu Likonen" <tlikonen@iki.fi>,
	"Ittay Dror" <ittayd@tikalk.com>,
	git@vger.kernel.org
Subject: Re: looking for "market share" analysis of SCMs.
Date: Wed, 21 May 2008 00:25:05 +0200	[thread overview]
Message-ID: <bd6139dc0805201525r22ba7398g6f341f89ae699b57@mail.gmail.com> (raw)
In-Reply-To: <alpine.LNX.1.00.0805201748020.19665@iabervon.org>

On Wed, May 21, 2008 at 12:07 AM, Daniel Barkalow <barkalow@iabervon.org> wrote:
> Doing it as a percentage is kind of odd; it demonstrates that using
> version control is decreasing in popularity as more and more people who
> don't use version control submit votes. All of the version control systems
> show an upward trend in number of users, but most of them are not growing
> as much as the market is shrinking. Unfortunately, there doesn't seem to
> be a way to get the people who use each of them as a percentage of people
> who use any of them, which is what you want for "market share".

Ah, you are right, I didn't analyse the graph enough, I thought
percent would show what you described above, obviously it doesn't
though as the values don't add up to 100%. Even so, I think this is a
better graph:
http://tinyurl.com/4hu2cn
Since it shows users that regularly use the package, instead of user
that have it installed. Considering that these days distro's have a
lot of stuff pre-installed if you go with the "coders packages" the
usage votes give a better picture than looking at who has it installed
(which includes people that don't use the package at all). That graph
shows that in the end of 2006 SVN became more popular than CVS,
whereas the one from Teemu (http://tinyurl.com/4vpqzg) does not show
that, probalby because a lot of people have it installed, but don't
use it.
It would be interesting if we could link the grow spurts from
http://tinyurl.com/4hu2cn to programming-related events, something
that might have caused people to suddenly use a VCS a lot more (for
example the one in CVS's line from 05-2007 till 07-2007).

-- 
Cheers,

Sverre Rabbelier

  reply	other threads:[~2008-05-20 22:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-20  8:57 looking for "market share" analysis of SCMs Ittay Dror
2008-05-20  9:20 ` Thomas Koch
2008-05-20  9:32 ` Teemu Likonen
2008-05-20 10:10   ` Sverre Rabbelier
2008-05-20 22:07     ` Daniel Barkalow
2008-05-20 22:25       ` Sverre Rabbelier [this message]
2008-05-21  0:24         ` Daniel Barkalow
2008-05-21  4:06         ` Linus Torvalds
2008-05-21  4:26           ` Martin Langhoff
2008-05-21  4:44             ` Sverre Rabbelier
2008-05-21  5:10               ` Martin Langhoff
2008-05-21  5:21                 ` Sverre Rabbelier
2008-05-21 19:39                   ` Robin Rosenberg
2008-05-21 20:07                     ` Daniel Barkalow
2008-05-21 20:28                       ` Teemu Likonen
2008-05-23  4:16                 ` Martin Langhoff
2008-05-21  4:40           ` Sverre Rabbelier
2008-05-21  7:20           ` Peter Karlsson
2008-05-20 22:34 ` Jakub Narebski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bd6139dc0805201525r22ba7398g6f341f89ae699b57@mail.gmail.com \
    --to=alturin@gmail.com \
    --cc=barkalow@iabervon.org \
    --cc=git@vger.kernel.org \
    --cc=ittayd@tikalk.com \
    --cc=sverre@rabbelier.nl \
    --cc=tlikonen@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).