On Thursday, April 4, 2013 1:29:07 PM UTC-6, Jonathan Vanasco wrote: > > A couple points from experience: > > More so than ORMs, random features, extensibility, flexibility, Magic > going on behind the scenes -- Pyramid lets the development team and > product managers decide where the Technical Debt and Bottlenecks will > be -- and is designed in a way that you don't have to scrap your > entire project when you're refactoring later on. You don't get that > in most other frameworks -- whether they're low level or high level. > > In order to get a project up and running in Pyramid vs Django/Rails > I'll often see something like this: > - Weeks 1-12, the higher level framework progresses much faster with > deliverable/usable features. > - Weeks 8-20, the higher level framework begins to deliver fewer > features each day. more work is spend configuring different plugins > and coding 'around' various framework options. the lower level > framework begins to pick up speed in delivering ticketed items. > - Weeks 20+, the lower level framework has a faster velocity in terms > of delivering features. > > Small projects - both for size and duration - are really great on > higher level frameworks . Django/Rails/etc are damn-perfect for > advertising campaigns, brand promotions, one-off online experience. > When it comes to online businesses and applications that span years, > high level frameworks start to be a huge concern. For example : > reddit is still on Pylons while Twitter has been increasingly > offloading more and more of its functionality onto C/Scala/etc. > today , twitter is much larger and more 'real time' than reddit, but > their need to refactor started years ago as did their problems with > being built on a higher level framework. > > I've never met a "Pyramid Developer". I've met many "Python > Developers" who use Pyramid. Conversely, I know many "Rails > Developers" and "Django Developers" , who would not consider > themselves to be "Ruby" or "Python" developers -- and largely aren't. > The bulk of their ability and work experience is with the Framework -- > not the language. >
I totally agree with what you said about "I've never met a Pyramid Developer. I've met many Python Developers that use Pyramid". I've been using Python for about a year now. Before that I was a java/groovy developer. I still do java/groovy for clients, it pays my bills. But for greenfield projects where I have carte blanche I have chosen Pyramid. Before delving into Python and Pyramid, I was assessing Rails then Django. Both frameworks seemed different than the language they were implemented in. And it required more time to be productive with it. While with Pyramid, I only had to learn Python and a small subset of how to wrap my application with Pyramid to expose it over a web interface. I'm very happy with that approach. I write my application as a pure python module that I can test independent of Pyramid, and my views are only thin wrappers that make requests to my application. Even the persistence layer is a separate module that is implemented with SQLAlchemy and I can test that independently and deploy upgrades, patches and new features independent of the web framework & the business logic. I don't even need to restart Pyramid. Just run python setup.py install on the module and it is deployed. I wish there was a port of Pyramid( & SQLAlchemy ) in every language. -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pylons-discuss?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
