Pyramid's small user-base worries me
I'm new to web-application development, and I've just started building a (relatively large) webapp. Thus-far I've been using [Django][1], however, I've just read about [Pyramid][2], and I really like the sound of it: Its documentation reads well, it seems to scale easily from small-to-large projects, it boasts great performance, and it's developers seem quite onto-it. All good things. It also seems quite flexible, which suits my needs well. However, I'm worried about Pyramid's user-base.

For instance, on stackoverflow, the "pyramid" tag has seen 6 questions this week, whereas the "django" tag has seen 247. I know that Pyramid developers are [committed to answering any questions developer's have][3], however, that doesn't completely put my mind at ease. I'm just not sure if I'll be running risks by choosing a framework which has such a drastically smaller community. My fears are this:

 - Not much "user" documentation
  - With Django, you can google how to do pretty much anything you want and you'll end up with a tutorial on somebody's blog somewhere in the world.
  - My fear is that even though the Pyramid documentation seems quite comprehensive, the moment you end up in territory not covered by the documentation, you're kind of on your own (until you submit a question and receive a response, which seems like a much more lengthy process than just reading a blog).
 - What if it disappears?
   - Django isn't going anywhere. I don't know enough about Pyramid to make the same assumption. What if I spend a year developing and maintaining this application, only to find out that in the meantime Pyramid support has died out, merged into a different project, etc.?
 - Hiring future developers for my app - most likely they will know Django, not Pyramid.
  - Maybe this won't be a huge issue if Pyramid has a relatively small learning curve for people who already know Django?
 - There might be other serious draw-backs that I'm not aware of for using a framework with such a young community.

Anyway, I'd love if an experienced developer could give me some feedback about all of this. How much of a risk would I be taking by choosing Pyramid over Django? and more generally, by choosing a newer technology over an older one?


  [1]: https://www.djangoproject.com/
  [2]: https://docs.pylonsproject.org/projects/pyramid/dev/
  [3]: https://pylonsproject.org/projects/pyramid/dev/narr/introduction.html#support
Pyramid's small user-base worries me
===

I'm new to web-application development, and I've just started building a (relatively large) webapp. Thus-far I've been using [Django][1], however, I've just read about [Pyramid][2], and I really like the sound of it: Its documentation reads well, it seems to scale easily from small-to-large projects, it boasts great performance, and it's developers seem quite onto-it. All good things. It also seems quite flexible, which suits my needs well. However, I'm worried about Pyramid's user-base.

For instance, on stackoverflow, the "pyramid" tag has seen 6 questions this week, whereas the "django" tag has seen 247. I know that Pyramid developers are [committed to answering any questions developer's have][3], however, that doesn't completely put my mind at ease. I'm just not sure if I'll be running risks by choosing a framework which has such a drastically smaller community. My fears are this:

 - Not much "user" documentation
  - With Django, you can google how to do pretty much anything you want and you'll end up with a tutorial on somebody's blog somewhere in the world.
  - My fear is that even though the Pyramid documentation seems quite comprehensive, the moment you end up in territory not covered by the documentation, you're kind of on your own (until you submit a question and receive a response, which seems like a much more lengthy process than just reading a blog).
 - What if it disappears?
   - Django isn't going anywhere. I don't know enough about Pyramid to make the same assumption. What if I spend a year developing and maintaining this application, only to find out that in the meantime Pyramid support has died out, merged into a different project, etc.?
 - Hiring future developers for my app - most likely they will know Django, not Pyramid.
  - Maybe this won't be a huge issue if Pyramid has a relatively small learning curve for people who already know Django?
 - There might be other serious draw-backs that I'm not aware of for using a framework with such a young community.

Anyway, I'd love if an experienced developer could give me some feedback about all of this. How much of a risk would I be taking by choosing Pyramid over Django? and more generally, by choosing a newer technology over an older one?


  [1]: https://www.djangoproject.com/
  [2]: https://docs.pylonsproject.org/projects/pyramid/dev/
  [3]: https://pylonsproject.org/projects/pyramid/dev/narr/introduction.html#support