> Beyond that, what I am wondering is how much users will be able to understand > how Django work if they can't do the installation.
Each year I accept foreign students for internship in my company and most of then either never heard of Django or didn't bother to learn how it works just to try it. Most of them were competent developers, but they didn't see the point of learning a how to get started with Django because it seemed too complicated to setup and use for starters. So they preferred to stay in their comfort zone: PHP. But when I gave them no other choices than to learn and use Django, most of them picked it up in less than a week and they "saw the light". Just last week my last intern wrote me on facebook to say he continued to use django back in his country and he think it's really awsome. The point is not to lower the bar for the "less gifted" as you imply, it's to lower the bar so more developers can give it a try without having to learn about every possible approaches and test them to see which one fits their needs. If they can get started and play with django with little efforts and they like it, *then* they will have a good incentive to spend time learning more about the many ways you can use and deploy it. I think that's what "lowering the bar" is mostly about. It's not about making it dumb-friendly by any means. regards On Sep 13, 2:07 am, Xavier Ordoquy <[email protected]> wrote: > Le 13 sept. 2011 à 05:44, Justine Tunney a écrit : > > > I agree with you that reducing the barriers to using Django is very > > important. But what we need is not necessarily a web based installer, but > > something to get people off the ground so they can start playing around > > with Django very quickly. Back in the day (like circa 2004) the thing that > > really helped me learn PHP was this program called EasyPHP which was a > > simple Windows based installer that got me up and running and writing code > > on my local machine in five minutes. > > PHP and Django installation are very different. > > For PHP you need a couple of things: > - apache or equivalent > - php module > - configuration tuning > - find the apache root to put your files under > - a database > - database modules for php > and I might have missed a couple of things > > For Django, you'll need: > - Python > - Django > > At this point you can go ahead with the dev server and sqlite. No need to > tune/configure things further. I hardly see how one can lower this further. > > Beyond that, what I am wondering is how much users will be able to understand > how Django work if they can't do the installation. > > Regards, > Xavier. -- You received this message because you are subscribed to the Google Groups "Django developers" 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/django-developers?hl=en.
