From: "Shawn O. Pearce" <spearce@spearce.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git User's Survey 2008 partial summary
Date: Wed, 3 Sep 2008 07:45:52 -0700 [thread overview]
Message-ID: <20080903144552.GA27682@spearce.org> (raw)
In-Reply-To: <200809031607.19722.jnareb@gmail.com>
Jakub Narebski <jnareb@gmail.com> wrote:
> This is partial summary of Git User's Survey 2008 [...]
>
> 03. With which programming languages are you proficient?
>
> Around 939 people answered this question. C is most popular with 59%;
> Ruby and surprisingly a bit shell script programming have around second
> place, with about 52-53%. More people are proficient with Python than
> in Perl by about 1/3-1/4. Very few people (25 responses, around 3%)
> feel proficient in Tcl/Tk, which means shallow pool of possible git-gui
> and gitk contributors. Java is quite popular with around 42%, which
> gives hope in continued JGit/EGit development.
Yea, I liked seeing that result from our user base. 42% of the
respondants know Java as a language. Not all of them may like
programming in it for fun, but at least they claim they know it. :-)
In the IDE part Eclipse received 13% (124 responses), which is
almost close to Emacs (20%, 193 responses). Sadly only 2% (19
responses) use EGit. There's probably a lot of reasons for that.
Possibly the "egit_sux" tag on repo.or.cz. Or our lack of a stable
update site that users can install reasonably stable versions from.
I think we've picked up 3 new contributors recently to the JGit/EGit
project. Jonas Fonseca has started to use JGit inside of a NetBeans
IDE plugin. Today he posted 2 patches, hopefully the first of many.
Tor Arne Vestb� has been working on improving EGit's resource
decorator. His fork on repo.or.cz is a few days old, but it has
some really good potential in there. I'm looking forward to seeing
the final series from his work.
Charles O'Farrell joined us a few weeks back and added support for
ref deletion, along with CLI for "jgit branch -d/-D". I think his
time is rather limited, but the contributions are most appreciated.
And of course Marek Zawirski is still contributing, but I think
he's back in classes so his time is a little bit more constrained.
Months back I think someone asked about including JGit in a
commerically licensed product. Since its 3-clause BSD its quite
possible to do. But I haven't seen anything materialize yet on
that front.
--
Shawn.
next prev parent reply other threads:[~2008-09-03 14:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-03 14:07 Git User's Survey 2008 partial summary Jakub Narebski
2008-09-03 14:45 ` Shawn O. Pearce [this message]
2008-09-03 15:20 ` H.Merijn Brand
2008-09-03 16:25 ` Felipe Contreras
2008-09-04 2:43 ` David Aguilar
2008-09-05 22:17 ` Jan Hudec
2008-09-06 4:17 ` David Aguilar
2008-09-03 15:00 ` David Brown
2008-09-03 15:41 ` Scott Chacon
2008-09-03 16:00 ` Jakub Narebski
2008-09-04 13:23 ` Git User's Survey 2008 partial summary, part 2 Jakub Narebski
2008-09-06 2:22 ` Git User's Survey 2008 partial summary, part 3 Jakub Narebski
2008-09-06 5:15 ` Shawn O. Pearce
2008-09-06 8:27 ` Andreas Ericsson
2008-09-07 23:07 ` Jonas Fonseca
2008-09-07 23:47 ` Shawn O. Pearce
2008-09-06 22:17 ` Git User's Survey 2008 partial summary, part 4 - how do we use Git Jakub Narebski
2008-09-07 8:31 ` Andreas Ericsson
2008-09-07 8:44 ` Jakub Narebski
2008-09-11 20:14 ` Git User's Survey 2008 partial summary, part 5 - other SCM Jakub Narebski
2008-09-11 21:03 ` Anatol Pomozov
[not found] ` <48C98F92.40903@workspacewhiz.com>
2008-09-11 22:05 ` Jakub Narebski
2008-09-11 21:54 ` Jeff King
2008-09-11 22:51 ` david
2008-09-12 10:44 ` Jakub Narebski
2008-09-13 21:11 ` david
2008-09-13 22:03 ` Jakub Narebski
2008-09-15 11:51 ` Mark Brown
2008-09-14 10:45 ` Nguyen Thai Ngoc Duy
2008-09-14 13:32 ` Jakub Narebski
2008-09-15 3:39 ` david
2008-09-15 7:00 ` Andreas Ericsson
2008-09-16 17:12 ` 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=20080903144552.GA27682@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.