To be fair I didn't say that Django isn't good for large projects, I said that I think it isn't as good as TurboGears.
I wholeheartedly think it's the second best web development framework for large complex sites (Rails is good too), which is saying a lot. Emphasis there on "I" and "think". Sweeping generalisations are often quite useful. Django is very good and you won't discover it's flaws until you've been using it a long time. A quick play around with it won't tell you anything about it. (same with TG). To go back to the comparison with SQLObject and SQLAlchemy. Once is very easy to get started in, and amazing for the small problems. The other is quite hard to get started in, but good for complex problems. That's not to say one is better than the other. I think that's fairly accepted opinion and most people on this list would agree (I think even Ian Bicking would agree). It's very useful information to people who are getting started. If your site is going to be simple, use SQLObject, otherwise it might be worth putting the considerable effort into learning SQLAlchemy. To clarify that I wasn't being excessively biased, I should point out that I did recommend he should use Django unless he was going to do something complex. That's the same advice I give to anyone who asks me (sometimes I don't mention TG as an option if I'm sure they're not right for it). I love TurboGears but I don't think it is entirely suited to beginners, particularly people without programming experience. Whereas I think Django is (or at least is more so than anything else). Ed On 7/30/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote: > > > Django is easy to get started in, and good for quick easy projects, > > but not so good for large complex projects. > > Now, I'm obviously biased (I'm one of the lead developers of Django), > so I I'm going to stay away from the "which should I use" question. > However, this blanket statement that Django isn't good for "large > complex projects" is a very unfair characterization. > > There are *plently* of "large complex projects" that use Django; the > one I'm most familier with is Ellington, the commercial CMS that Django > was extracted from. Sloccount reports that it's around 50k lines of > Python code in around 1k files, and I can tell you right now Django > suits it just fine :) I could name any other of other large projects, > but I won't bore anyone. > > Point is, the best way to figure out which of these (or any!) tools > suit you is to download 'em and play around. Free Software rocks that > way :) Oh, and if you're a VMware user, a great way to get started > playing around is to download the Python Web Developer VM > (http://www.vmware.com/vmtn/appliances/directory/289); it's got just > about every Python web toolkit pre-installed, and it's super fun for > messing around with. > > The point is that sweaping generalizations without any facts or > specifics to back 'em up aren't worth the (virtual) paper they're > printed on. Trust your own judgement. > > Jacob > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears" 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/turbogears -~----------~----~----~----~------~----~------~--~---
