We've been using Pyramid for the last 2.5 years at our startup, having built it from the ground up. I'm always amazed at how much code we get to reuse through each iteration of the site. In addition to that, we have never had to work against the framework, we've always just been able to build on top of it.
On Tue, Dec 9, 2014 at 10:04 AM, Paul Everitt <paulwever...@gmail.com> wrote: > I think this is a reasonable and useful post. Likely moreso than this > response. :) > > It’s quite useful to look at the “whole product” instead of just the > “product” (to use jargon from Crossing the Chasm.) Can you get enough > ecosystem for the surface area of the thing you are using? > > One factor that mitigates against this, though, is when you are building > your own thing with its own surface area. If your thing is small, and most > of the surface area you need to deal with is in Pyramid/Rails/Django/Flask, > then that’s the place you need sanity. > > But if *your* thing has a big surface area, then *your* thing needs > sanity. Pyramid is very good at this framework-framework picture, helping > you build your own thing that is sane. > > Not only that, but Pyramid by definition attracts people to its community > that care about those issues: scalable, maintainable systems that are > well-built by adults. Other systems might win on quantity, but a > distressingly high percentage of those have a distressingly naive worldview. > > —Paul > > On Dec 9, 2014, at 10:52 AM, Jacob Hite <jrh...@gmail.com> wrote: > > Building a startup with a small team, how to decide between using Pyramid > (or possibly Django) or Ruby? > > This may be an impossible question to answer and I'm probably asking on a > biased list. > > I've worked a lot before on Pyramid and generally like it. It was fast and > very flexible, but missing some things (Django's admin...). The missing > things though are usually the key to Pyramid's flexiblity. There also seems > to be some cruft left over from repoze and other stuff that seem out of > place and ugly in the elegant Pyramid world. > > I've never written any Ruby or RoR other than trivial tutorial code, but > it seems fine and just as sufficient as Pyramid. I do slightly prefer > Python language syntax, but I can get over that. > > My main concern is working with a framework that has a great online > community and actively moving forward and has lots of experienced > developers to hire from. > > When I look at Google and Github trends and look at StackOverflow tags, > RoR overwhelmingly beats Pyramid. I think this is due to Python being so > fractured. Many competing frameworks (Django, Pyramid, Flask, Bottle, etc, > etc) probably lower Pyramid's trend and tag levels. Django certainly > dominates Python web frameworks. > > In Github I still see lots of active commits to Pyramid. But I'm a bit > concerned, and I can speak personally on this...most of the most big name, > active Pyramid contributers seemed to have disappeared from answering > questions on StackOverflow. > > I guess I'm trying to get a solid handle on the current state and progress > of Pyramid. Can anyone point me in the right direction here? > > Is it time to slide over to Django or make the jump to RoR? > > I have a personal preference for Pyramid because of positive past > experiences with it and lack of experience with other frameworks. But this > isn't about me. This is about building out a startup company quickly and > being able to attract experienced talent with the decided on technologies. > > Apologies for the long-winded, open-ended question, but I would appreciate > any responses that can give me a 'heartbeat' on the current Pyramid state > of the union. > > Many thanks in advance. > > > > > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pylons-discuss+unsubscr...@googlegroups.com. > To post to this group, send email to pylons-discuss@googlegroups.com. > Visit this group at http://groups.google.com/group/pylons-discuss. > For more options, visit https://groups.google.com/d/optout. > > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to pylons-discuss+unsubscr...@googlegroups.com. > To post to this group, send email to pylons-discuss@googlegroups.com. > Visit this group at http://groups.google.com/group/pylons-discuss. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to pylons-discuss+unsubscr...@googlegroups.com. To post to this group, send email to pylons-discuss@googlegroups.com. Visit this group at http://groups.google.com/group/pylons-discuss. For more options, visit https://groups.google.com/d/optout.
