I've built dozens of sites over the past 14 or so years , with Ad Agencies, Large Brands, Tech Startups, Major Media companies.
Doing this, I've learned that Frameworks are really really great for the run-of-the-mill project that has a quick deadline, doesn't do anything new & exciting, and has a shelf-life ( ie, it's expected to last 6-18 months and then it gets turned off ). For anything that needs constant improvement, nurturing, active product development and scaling of user interactions... frameworks have always been a complete fucking nightmare. Time and time again, I've seen my colleagues hit their heads against a wall ( often literally ) and wasting countless cycles trying to get around a 'design' or 'convenience' of a framework. I've also often seen months of work for projects that built on a framework thrown out and replaced with entirely custom Java/C/Python/etc code to solve the issues. I'm a big fan of using the right tool for the right job. If I'm needing to do a simple project that a 'framework' can quickly get off the ground and not need to maintain/grow it outside of that framework -- fine! But I'm well past the point in my career where I can justify saving an extra week off the initial launch plan to go with a convenience framework, when I know that I'm damning my dev staff to mundane and crap tasks like spending a week to customize a pagination plugin to work within the confines of that framework. I became a huge fan of Pylons/Pyramid , because a large majority of the stuff that lead people tend to abandon frameworks during project growth can be - and is easily - done within the environment. On Dec 13, 4:59 am, rihad <[email protected]> wrote: > So it's a perfect tool for writing a framework :) > Lightweight in my understanding means few features, mostly glue code. > Just like Pyramid. All other meaty, but nonetheless important > features, are meant to be chosen by a developer using that framework, > and plugged in. For example, AFAIK Pyramid has no Form/validation > subsystem in its core, or even an "official" plug-in that it endorses. > Through trial and error, you have to just pick the missing part from > the plethora of what's available, that would suit you functionally and > esthetically. Maybe in the long run this would make you a more savvy, > professional developer. But you'll have to agree with me, that if our > goal is to build bigger, less buggy programs, we're gonna have to > abstract from smaller details, use bigger bricks, so to speak. That's > why people have chosen C, not assembly to write most parts of a larger > OS; PHP, Perl or Python over C for web work, Frameworks over plain > PHP, Perl or Python to facilitate building even larger programs. And > that's because a human, however smart he or she is, cannot hold all > the miniscule details in his head. People can see the bigger picture > more clearly. So unless there's a larger framework built on top of > Pyramid, as it is now the learning curve of getting the needed tools > and do some CRUD/DB/auth/form edit/add, lists/pagination with some > custom functionality - is pretty slow. -- 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.
