First, I've recently setup a Dreamhost account myself with no problems -- feel free to email me directly if you want some help, and I'll see what I can do.
That said... Django and Python are still going through growing pains in the shared hosting department. The same thing was going on with Ruby when Rails first started gaining popularity. It's a trade off you have to deal with for relatively young platforms like these. PHP started getting popular back around '98. Of course it's going to have more support. Whether or not Django is the way for you to go is a personal decision. To use your Linux analogy -- you have a piece of hardware. It will run plug-and-play on Windows. It will also run on Linux, but only if you download a custom distro and compile some drivers and make some low level changes to the kernel... big pain. But once you do it, it performs 3x better on Linux than it does on Windows. Is it worth it? It depends on how much you plan to use the hardware and what the requirements are. The same goes for Django. If you're building a complex site that you will be doing administration for and long term development on, Django may be worth any trouble you're having up front. If you're just banging out some quick project that won't have to worry about later, use whatever is easiest. On Jul 23, 2:28 pm, walterbyrd <[EMAIL PROTECTED]> wrote: > On Jul 23, 12:38 pm, Tyson Tate <[EMAIL PROTECTED]> wrote: > > > On Jul 23, 2007, at 11:23 AM, walterbyrd wrote: > > Blaming Django for FastCGI problems on discount-rate hosting services > > I don't "blame" Linux for not running all the newest hardware, but if > need a certain piece of HW, and Linux doesn't support it, then I'm not > using Linux. > > BTW: I do use Linux. But, the point is: it isn't about "blame" it's > about "does this work for me." > > Bottom line: Dreamhost is actually better than a lot of shared > hosting. And PHP frameworks are much less hostile to shared hosting. > I'd like to use Django, but at some point I have to wonder if it's > worth all the extra trouble and expense. > > Unless you go with some special site that installs django for you, > django's setup tends to be complicated - lots of steps, many possible > points of failure. And when you follow some tutorial, no matter how > good it is, there is usually no where to turn if it blows up in your > face. And even if I manage to get django installed, I have to contend > with oddities like restarting the server when I change the code, or > touching all the files, or something. Setting up a PHP site, by > contrast, seems trivial. > > Django still may be still be worth it, but it is something to think > about. --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
