3 ms·
Ahh! Yes, that's a perfect match for the given context. Thanks! I question the assertion "Django is older and larger, but Flask has a more active community acc
by dalke 12y ago
Ahh! Yes, that's a perfect match for the given context. Thanks!
I question the assertion "Django is older and larger, but Flask has a more active community according to GitHub." Surely the number of stars and watchers don't mean that those people are active in the project. According to the github pulse reports for the last month:
> Flask (March 23, 2015 – April 23, 2015): Excluding merges, 19 authors have pushed 23 commits to master and 69 commits to all branches. On master, 16 files have changed and there have been 340 additions and 43 deletions.
> Django (March 23, 2015 – April 23, 2015): Excluding merges, 124 authors have pushed 189 commits to master and 608 commits to all branches. On master, 2,395 files have changed and there have been 25,689 additions and 84,146 deletions.
By those numbers it seems that Django has a much more active community, in the sense of making code changes. There are other types of activity than code commits, like support, conferences, etc. I don't get the sense that Flask is more active there either.
Edit: If it is meant as an allusion to the Mac/Apple][ era at Apple then activity is a poor measure - there was much more activity and general interest in the Apple ][ during the Mac development.
- pyre 12y agoPart of the problem with comparing commits is the Django is more comprehensive. There is a larger "surface area" to make changes to.
- dalke 12y agoThe question really is, what's a useful way to determine which of two projects has a "more active community according to GitHub"? Is the number of stars/watchers a good enough proxy to use for decision making? The projects I use are typically quite small, and my code is on Bitbucket, so I have effectively no experience in this.