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

Re: Git User's Survey 2008 partial summary

From
JHJan Hudec <bulb@ucw.cz>
Date
Sep 5, 2008, 22:17 UTC
Message-ID
<20080905221731.GI15520@efreet.light.src>
In-Reply-To
<402731c90809031943n181ad6fbw366f90e80aaca2a@mail.gmail.com>
On Wed, Sep 03, 2008 at 19:43:20 -0700, David Aguilar wrote:
Show 32 quoted lines
> On Wed, Sep 3, 2008 at 9:25 AM, Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
> > On Wed, Sep 3, 2008 at 6:20 PM, H.Merijn Brand <h.m.brand@xs4all.nl> wrote:
> >> On Wed, 3 Sep 2008 07:45:52 -0700, "Shawn O. Pearce"
> >> <spearce@spearce.org> wrote:
> >>
> >>> 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.
> >>
> >> Rewrite them in perl or python and get more patches?
> >> The fact that it is not perl withheld me from finding solutions to
> >> problems I still have with the git-gui gitk combination
> >
> > Ruby!
> >
> > --
> > Felipe Contreras
> 
> There's already a python git-gui:
>     http://cola.tuxfamily.org/
> 
> PyQt is a very mature library, which is one of the primary reasons I
> chose Python.

Sorry, but I disagree. Tried PyQt, been hugely disapointed. Boils down to any thing that can make Python (or, for that matter, any) interpreter segfault being totally broken.

But as far as Qt goes, I would really just stick with C++. Python or Ruby have some advantage, but I am not sure it's that big to offset the fact, that a lot of code already exists in QGit.

> Does Ruby have any good and mature UI libraries?  I know it's all the
> rage for web stuff, but I haven't heard too much about people using it
> for GUIs.

Qt? I believe Ruby Qt bindings are in better shape (properly handle Qt deleting objects under Ruby's hands).

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>
Previous: David AguilarNext: David Aguilar
Message 6 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.