On Mar 25, 1:47 pm, Chris McDonough <[email protected]> wrote: > Errr. I've written a Django app, and it wasn't anywhere near like just > changing a config file. It's a lot like writing an app under any other > web environment... requests, view callables, templates, integration with > 3rd party libraries and system processes, etc. Pyramid and Django, > where they overlap, are very similar, and developers face the same > problems and use similar solutions.
*you* might have, but the majority of django apps i've seen are much more "step and repeat" and "write to django". i'm not talking about what you *can* do, but what most people do. very few touch system processes or non "django-" libraries. the coding style is typically very enforced , which is great... but when you see code from some django apps, there's very little Django and a host of plugin/ configuration calls + database/form schemas. a good example is the TastyPie library for API management. So much has been abstracted. The bulk of the work is more akin to "configuration" than programming. ( http://django-tastypie.readthedocs.org/en/latest/tutorial.html ) I've sidetracked this conversation enough. all of Chris's ideas are great. "creating highly scalable web applications with pyramid" is also buzzwordy. -- 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.
