Rapid Rails or Django Development?

Question

I have about 2 weeks of real-time development to release a contact database system to replace various spreadsheets and pieces of paper around.

you will also need to develop two websites (with dynamic content) and a small AJAXian web service

I have no experience with rails or django, but you can learn quickly ..

both pretend to be about quick development.

What are these rails that django does not have, and vice versa, which will accelerate the development of this application?

Also, the contact database is more dependent on the admin panel (dj) or forests (ror)? (there will be many CRUD operations)

thanks

Daniel

---

Hey guys, thanks for your wonderful answers that I was going to try N, use this as a benchmark for performance performance. I'm actually a .Net guy, but this database will be better on openource, and I'm not too keen on mono: P thanks, I rethink and reallocate the time !;)

Answer 1

Without experience in one, in just two weeks, to deliver a product, I would not choose. If you have a limited time, you need to use what you already know. You will need two weeks to settle in any setting. Rails and Django are popular and make it easy to cope with a small amount of time due to the amount of detail that runs for you in the background, without having to think about it. If you do not know what these details are, you will not be able to use the capabilities of any platform, and you will have a code base, which is a confused mess of code that you do not use, which will affect maintainability.

I am making a @knutin comment on the ease of deployment with Rails. That might have been true a few years ago, but today the Rails application is pretty easy to deploy even on a bare server, and if you plan on deploying it to Heroku it's even easier. As far as I know, there is no django application platform that offers something like scalability or ease of deployment that the hero and rails offer.

If you are dead when doing one or the other, I would recommend using rails using formtastic to create your CRUD forms. Formtastic offers much more flexibility than the built-in Rails flyover generators, so you can come back and improve it while still using them.

Finally, if you decide to use something, despite the learning curve, I heard a lot of good things about hobo although I have not used it in the project yet. It may be easier for you to get started with Rails.

Answer 2

The Django administrator will create a CRUD application that you can customize to meet almost any need from your model definitions. I used the administrator for the main user interface for several projects and I can tell you that this is a real time-break. You do not need to spend time creating templates or Javascript.

Django also has general views that can execute object details, view lists, update or delete on any model without worrying about application logic. You simply supply the templates, connect to the URLs and basically execute.

For deployment, I would say that Django and Rails are now equal. The rails were sick to deploy, but things changed a lot.

For a simple contact database, the admin might be the biggest difference between Rails and Django. And the fact that you can run the Django project locally, with a real web server without any configuration ("python manage.py runningerver").

Answer 3

if you are definitely not equally experienced in both cases, you should definitely use the one you like best. If you don’t know any python, and you don’t know a single ruby, then you probably should not use it either. If you know PHP, you can get similar results with CakePHP or CodeIgniter. If you speak another language, you can ask about Rails, how is the MVC structure for this language on this website

Answer 4

This article has a good comparison, in which two developers participate without prior experience with any framework: https://docs.google.com/View?docid=dcn8282p_1hg4sr9

Answer 5

This is a question that I'm still trying to find the answer too, that is what I can tell you so far.

Introduction When it comes to langauges scripts, I always prefer python, not only do I feel stronger using python, but libraries are better and faster. Also (and Ruby developers have something to say). I find Python more comprehensible and readable by code, which is Ruby.

Said Rails is a great infrastructure! It has a lot more “magic” than Django, and now with Rails 3 you can write your ajax in unobtrusive Javascript, which makes it beautiful to read. Also, path and form functions are much better than Django.

The big problem is this: since I said that Rails does a lot for you (aka magic), the only problems are that if you want to avoid these conventions for some reason, you find yourself dealing with a lot of problems, and with Django you have more control over your application.

Django also has a Super-hardcore Admin and User app, you don’t need to install any plugin, this is ALL for you! Setting up users is incredibly simple, and the admin backend gives you CRUD for each model.

In general, I prefer Django, I understand it better, and it does what I say, although I have to say that as far as this is happening now, Rails will have more support in the future.

Feel free to ask any questions !! Hope this helps

Dan