Whilst I believe that Rails would save me time by being quicker to develop, I can’t just dive in and use it on a commercial project without doing a few dry-runs on non-critical stuff. There’s just no time to make mistakes and try things out in the current environment. Catch 22:- I have no time to learn how to save myself time :-)

> Django has that built in in spades

Right… Where? And how should I use it? Or, rather, where should I look to find how to use it?

Adrian Holovaty’s answer to the Django-users mailing list is “documentation is planned, if you can’t wait then check the source”.

So, I guess my answer to “what is stopping you from using either?” is “I want to use Python instead of Ruby, and Django isn’t accessible enough yet”.

I’ve read it, and it is by and far the most comprehensive documentation available for Rails. Many of the questions I see asked on the #rubyonrails channel are easily answered by anyone who has read the book. The problem is that the knowledge is in the book only, not on the web.

Outside of Zope, not a single Python Web Framework has had book written on it, interesting, no? (If there has been, I’ve never seen it on a bookshelf anywhere)

Django has that built in in spades – but for Rails, you have to look to something like the salted hash login generator.

I don’t know if you’ve heard this before, (Although it’s been said many times in many ways) but all code lives and dies by its documentation. Django is just starting up and doesn’t have everything documented because most of the features are broken or in flux. Ruby on Rails is fixed, but all the documentation I find is either tutorials that go just far enough to not be useful or the API reference which is confusing and poorly written. This seems to be normal for Ruby projects. Before this, I had nothing to do with it. If the Pragmatic Programmers would do a book on Rails, then I’d consider it.

For example, does anyone know how to have users and give them privileges and restrictions?

http://feh.holsman.net/articles/2005/09/28/whats-stopping-me-using-rails-django

basically none of them are really can be fixed by ‘code’ or ‘IDEs’, more things that projects like locomotive http://locomotive.sourceforge.net/ attempt to addresss.

You could have said the following and looked less of an idiot:

“Marshmallows and jumpsuites. Are these two fellows friends of django? Prove this”.