Alex Marandon wrote: > 2008/12/6 zunzun <[EMAIL PROTECTED]>: > >> Seems like I should use Django? Or should it be Pylons instead? >> > > Here is the advice of an average programmer with no emotional > involvement in any of these projects. > > I think it depends on your background. The Pylons ecosystem is very > powerful but it's quite complex and not really suitable for beginners. > I'm not sure there is a good framework for beginners. If your a beginner to python, then starting with web design will only make it harder. If you a beginner to python web frameworks then pylons might not be your first choice only because it is complex and lets you do almost anything you want (even if its wrong). Starting with Django or TG might be a good idea. I stated with Webware (it made a lot of scene especially coming from a php background), but now I do most everything in pylons because of the power. With Pylons the simple stuff is pretty simple (once you get beyond setting up your first application) and the complex stuff is possible. I really think its the same with any web framework, the better ones are complex by their very nature, after all we're building applications where we often have to user multiple "languages" to get the desired effects, serverside code for logic and data modeling, template code to generate a view and javascript to add ajax or just make the application look the way you want it to. Frameworks like pylons do their best to help you separate the three, other frameworks (Webware, php) let you mash it all together. So the long answer what is better, it all depends on what you want to do, how you want to do it, and where you are in the beginner-expert range (me I'm in the middle, not an expert yet, but I do ok). I don't like Django because I deal with lots of legacy data, an administrative staff that is constantly changing the system requirements, so even though sometimes things might be simpler to do in something like Django, in the long run I find Pylons easier to deal with and modify. > If it's going to be the first web framework you use, you should > probably stick with Django or even better Rails. If you're a seasoned > web developer used to get acquainted quickly with new APIs and want a > maximum of flexibility, then Pylons is for you. Don't let the size of > the community fool you, when it comes to technical advice quality > matters more than quantity. > I agree, this group although not huge, is usually very helpful and committed to helping folks use pylons. the problem is not that people don't always get an answer, its that they get multiple answers, different ways of doing the same thing, and to a noob I could see how that would be confusing.
> > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
