If you're doing something more like a run of the mill website there's less concern about which framework you choose.
But if you are going to scale or use large data stores and use alternative's to your SQL DB and really push the limits there's a lot of considerations that I'm not really up on . . . but you should either understand these or find someone else that does ( not me :-0 )
Doug
On Tue, Jun 26, 2012 at 9:59 AM, Kurtis Mullins <kurtis.mullins@gmail.com> wrote:
If you are doing the work yourself, use whichever you prefer. If you are paying someone else to do the work, give them the freedom to choose what to use. Just find someone who can complete the task at hand within your budget and the toolset really shouldn't matter -- as long as they're not doing it in some manner that no other developer will ever touch the code base.--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
No comments:
Post a Comment