Thanks Jon. I have plenty of ammunition, having used Drupal extensively in the past when I needed the work. I'm well aware of it's warts ( oh so painfully aware! ).
It's mostly that I think I need to back that up with some hard data too, ie: these sites are using Pyramid, it's for real! thanks Iain On Wed, Feb 15, 2012 at 5:09 AM, Jonathan Vanasco <[email protected]>wrote: > i wrote a long response yesterday, and it seems it didn't post. f'ing > google. > > The Pylons list is here: > > http://wiki.pylonshq.com/display/pylonscommunity/Sites+Using+Pylons > > For your purposes I would just talk about Pyramid being the new > versions of Pylons. There are plenty of large sites in there proving > it's battle tested and "enterprise". > > Aside from that, I would focus on the low cost-to-change and cost-to- > iterate that Pylons offers your group. and that that your team feels > they can deliver something of higher quality on a faster timeline than > on Drupal. > > I'd note that Pyramid/Pylons is aimed at developers and gives you the > tools to rapidly iterate on the product, along with the power to make > sweeping changes at a very low level -- both on the app and the > database. > > I'd also note that Drupal is architected for non-developers to > manage. It tries to do everything out-of-the-box and everything else > through admin interfaces to "modules", which means you have to write > and integrate modules to their various hooks. It's a complete pain in > the ass, and while the tiny non-profits that use it are ridiculously > happy (and should be)... all but one 'enterprise' user I know of look > at it as a huge mistake and have been jumping off. > > One of my consulting clients is a medium size publisher and migrating > from Drupal to Django right row -- and being on drupal held them back > for a few years. A huge cost to change and even larger to do tests/ > qa. An example is tat even the smallest things like getting a > Facebook/Twitter button on an Article would take 3-4 days to > implement. Why? Aside from not having a MVC/MT/etc system that had > nice templates and workflow, it's a mess of "theme" files that have a > few "container" files ( which barely go beyond <body></body> ), and > then lots of hooks and spaghetti code to fill the body tags. > > One of the other issues they had with Drupal is the Database structure > is far from optimized and can often jam up. Due to the essence of how > drupal works, they couldn't rewrite the database queries or modify the > table structure into something that is in-line with their usage -- > they're stuck with an off the shelf implementation that does things in > a particular way... so they have 20+ mysql queries to generate a > page, whereas with pyramid they might have 4 database queries... and > typically cache the results of 2 into memory. > > -- > You received this message because you are subscribed to the Google Groups > "pylons-discuss" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/pylons-discuss?hl=en. > > -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
