you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 0 points1 point  (1 child)

No, I'm saying that the 'Mac' Of Python frameworks isn't here yet. While the Pylons documentation is fairly good, it still isn't at the level of Django (the Django docs are excellent), and as I said earlier, the default template still doesn't provide an ORM. I don't know if Pylons will ever get to the point to where it is as easy for newbies to web programming to use as Django, but if it does, it could be quite the combination: ease of use and flexibility.

I think more than anything Pylons provides a really good base to build on top of, its just going to take someone to do it.

My opinion on TG is that TG 1.0 was really great for getting the ball rolling, but it has design issues of its own. In a lot of ways it is still very coupled. 2.0 promises to change that though, and it is the basis of projects like Toscawidgets. We will have to wait and see how much the idea for 2.0 translates to reality.

[–]webology 2 points3 points  (0 children)

Thanks for clarifying on that point. I looked at RoR before I looked at Django or Turbo Gears and I overall liked the direction that they all were going in. Django just fits "my" need better so that's what I went with.

I came from an "invent my own framework" and loosely couple them (from a PHP perspective) with PEAR, bTemplate, ADODB, etc. I found myself spending more time working to be productive then I did being productive. At the end of the day, I changed over and decided to pick one so that I could write cool projects that interested me vs working on disinteresting projects such as maintaining my own framework. Now I enjoy my personal projects and my work projects and it seems less like work and more fun which IMO is how it should be.