Skip to content

GUI Clients: Order by popularity #975

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Mar 6, 2017

Conversation

smith-kyle
Copy link
Contributor

This is a first step towards addressing #804

Here's the popularity order as determined by Google Trends 12 month view.

  1. SourceTree
  2. GitHub Desktop
  3. TortoiseGit
  4. GitKraken
  5. GitUp
  6. SmartGit
  7. Git Extensions
  8. Tower
  9. gitg
  10. GitX-dev
  11. Aurees
  12. git-cola
  13. Gitbox
  14. Cycligent Git Tool
  15. GitEye
  16. Fork
  17. GitAhead
  18. giggle

It's difficult to rank Fork with Google Trends. Even using the term "git fork" wouldn't be accurate since most results relate to the GitHub fork feature. I used "git-fork" instead.

This also changes the CSS of the list so that the links are displayed in the format:

1 2    rather than    1 3
3 4                   2 4

Reference:

Modifed CSS to list GUIs in the order that they appear on the list. Rather than:
1 3
2 4

It's now:
1 2
3 4
@peff
Copy link
Member

peff commented Mar 6, 2017

This looks good to me. Thanks for working on it.

I think ranking by Google Trends is a pretty reasonable metric, absent any other data (though if somebody with a vested interest wants to argue against it, I'm happy to listen). We'll probably need to revisit this periodically to get updated trends numbers. It would be nice if that could be done automatically, but probably not worth the boilerplate and hassle it would involve. I'd expect this needs to be re-done no more than once a year.

The CSS changes look like an improvement. I don't know if there are any gotchas with forcing a 2-column layout with these 49% divs or not, but it seems to work fine for me with a couple browsers at a couple different sizes.

We'll need to prebuild the assets before I can push this to heroku, I think. I'll take care of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants