Skip to content
This repository has been archived by the owner on Jun 20, 2018. It is now read-only.

Reasons for new projects to use gargoyle instead of gutter? #86

Open
rightaway opened this issue Jul 7, 2014 · 1 comment
Open

Reasons for new projects to use gargoyle instead of gutter? #86

rightaway opened this issue Jul 7, 2014 · 1 comment

Comments

@rightaway
Copy link

If we've never used gargoyle or gutter on any projects before and would like to use one on a new project, should we definitely use gutter? Or are there any features or functionality or any advantages to using gargoyle over gutter?

@NorthIsUp
Copy link

Gutter is the system that the maintainers are currently investing their time into.

a quick comparison:

  • Gutter is roughly feature complete with Gargoyle. (I have not done a line by line comparison)
  • Gutter is faster when using redis, or zookeeper.
  • Gutter works in any python application.

Those are reasons to use Gutter, the reasons against it are mainly it is newer and probably has some bugs.

  • Gutter is newer and has fewer users. This being said Disqus uses it in production at scale.
  • Gutter is a little harder to set up.

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

No branches or pull requests

2 participants