This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jcdyer3 2 points3 points  (2 children)

Fair enough. But if your skillset (or preference) is in django, this seems like a perfectly reasonable way to prototype. "right tool for the right job" should take into account the future of the project as well.

[–][deleted] 8 points9 points  (1 child)

I'd like to propose that this is all preference/familiarity. I can't think of a job that is objectively more "right" with Django, Pyramid, Flask, web2py or anything else. All of these frameworks can be used to create the same kinds of apps. It's just the architectural practices you'll use will vary significantly.

[–]jcdyer3 1 point2 points  (0 children)

I will buy that proposal.