Django vs RoR...?

Question

Web development

NOT HOLIVAR!
Yesterday I tried to lift the rails from a show-off, and was dumbfounded by how everything was thought out and cool with it!
I myself write in python, naturally django, but after trying the rails, I think to switch, but the question arose - is it worth it? (I've been writing in python for so long)
I want to ask those who wrote in ruby ​​and python, what do you prefer, because. in terms of demand, they are the same. Thank you!

Answer 1

I started with Django, but one day I came across rails and this tutorial and fell in love with them.
Why Rails?
- Rapid development. Rails puts this at the forefront, and at the same time, Rails scales pretty well.
— Ecosystem. For rails, a whole cloud of gems for all occasions. Devise, Gon, Mongoid, Rails_best_practices…
- Testing. Just try gems like RSpec, Cucumber, Capybara.
- Language. After a simpler python, I was a little afraid of a language with a bunch of special characters, as it turned out, in vain :) Well-written code reads like text in English, especially when using DSL.

Answer 2

Moved from Python (Flask, Bottle) to Ruby (Sinatra, Rails). I don't regret it. In terms of web development, IMHO, the Ruby ecosystem is better developed.

Answer 3

Here is my short story. I mainly write in php.
On django, I made a real estate portal with multilingualism, complex filters and much more, it was interesting,
I didn’t have time to submit the project on time, but django pleased with its flexibility and there were no problems with finding solutions.
and recently I also made a portal on rails, but much more functional. news, posters, search by enterprises, in general, there are also a lot of different functionalities. Guys, this is the first project that I submitted on time, and all the code is covered with tests,!
it was cool. moreover, I knew ruby ​​basicly and learned a lot in the course of development.

Answer 4

Write in what is convenient and what you use most often (including the language). I had a great opportunity to implement a project on jung and on rails. A project with a large spreading API was originally in jung, then with burning eyes I implemented it on rails in a couple of days, I was delighted that everything was out of the box, programming based on conventions, REST full api is described right there in the controller, a bunch batteries for all occasions, addiction tracking. It seemed crazy to me that the core developers of Junga refused to break compatibility in favor of speeding up the introduction of new features. Plus ruby ​​on which everyone made a bunch of convenient DSLs for all occasions. But after a long life of the project, I realized that I really lack experience with rails, and even more with ruby, my main language of work is python + a huge wave of tasks on js (full-fledged web applications with big logic), and when tasks for a project with rails arose again, I felt discomfort from the fact that simple tasks required a lot of time. Then there was dzhanga again, it already seemed so familiar, I know almost all its corners, and with greater confidence I can solve any tasks assigned to it. Junga doesn’t have that variety of batteries and chips out of the box, so it’s worth paying a little attention to finding solutions to the problem before writing code. Management of statics, migrations, deployment, everything is decided by batteries, no worse than on rails. When I began to notice routine tasks that were solved on rails, I tried to find solutions, usually it takes 5 minutes of searching or coding (most of it is solved by the factory). and when tasks for a project with rails arose again, I felt discomfort from the fact that simple tasks required a lot of time. Then there was dzhanga again, it already seemed so familiar, I know almost all its corners, and with greater confidence I can solve any tasks assigned to it. Junga doesn’t have that variety of batteries and chips out of the box, so it’s worth paying a little attention to finding solutions to the problem before writing code. Management of statics, migrations, deployment, everything is decided by batteries, no worse than on rails. When I began to notice routine tasks that were solved on rails, I tried to find solutions, usually it takes 5 minutes of searching or coding (most of it is solved by the factory). and when tasks for a project with rails arose again, I felt discomfort from the fact that simple tasks required a lot of time. Then there was dzhanga again, it already seemed so familiar, I know almost all its corners, and with greater confidence I can solve any tasks assigned to it. Junga doesn’t have that variety of batteries and chips out of the box, so it’s worth paying a little attention to finding solutions to the problem before writing code. Management of statics, migrations, deployment, everything is decided by batteries, no worse than on rails. When I began to notice routine tasks that were solved on rails, I tried to find solutions, usually it takes 5 minutes of searching or coding (most of it is solved by the factory). I know almost all its corners, and with greater confidence I can solve any tasks assigned to it. Junga doesn’t have that variety of batteries and chips out of the box, so it’s worth paying a little attention to finding solutions to the problem before writing code. Management of statics, migrations, deployment, everything is decided by batteries, no worse than on rails. When I began to notice routine tasks that were solved on rails, I tried to find solutions, usually it takes 5 minutes of searching or coding (most of it is solved by the factory). I know almost all its corners, and with greater confidence I can solve any tasks assigned to it. Junga doesn’t have that variety of batteries and chips out of the box, so it’s worth paying a little attention to finding solutions to the problem before writing code. Management of statics, migrations, deployment, everything is decided by batteries, no worse than on rails. When I began to notice routine tasks that were solved on rails, I tried to find solutions, usually it takes 5 minutes of searching or coding (most of it is solved by the factory).
And at present, nodejs is gaining simply gigantic popularity, which has just a gigantic number of batteries that no one has analogues.
I'm all about the fact that you need to choose an instrument with a head, the one that is more familiar, preferably written in your main language. But if there is an opportunity to try everything that brings joy, I am very grateful to my superiors who gave me this opportunity.

Answer 5

The undoubted advantage of rails is a gigantic ecosystem, a symbiosis of different gems, many conveniences for bringing to production and testing. In terms of testing, IMHO, he has no equal here. For harsh production and complex projects - that's it.
PS However, if I need to write something for myself, I choose python and something minimalistic, like webpy.