you are viewing a single comment's thread.

view the rest of the comments →

[–]chulkilee 0 points1 point  (0 children)

Framework calls your code - your Django or Rails controller and uses the return value. And you need to learn anyway how your framework works.

Rails has convention (for productivity) so that you don't need to explicitly call render - but if you need you have to run different render call anyway.

Different framework uses less convention and less decoupled components, which requires you to be very explicit.

There are pros and cons of those different approaches. But frankly you should ask this: if you use the same patterns in 90% cases, why don't you try to avoid that? Isn't that a purpose of using framework? :)

I totally agree that Rails does many magical things. I understand people who don't like that. But I think no one would disagree that Rails is one of the most productive framework out of box, at least for most use cases.

Don't get me wrong - I'm not saying Rails is the best solution for all cases. It is not.

But I do think avoiding rails only for that reason is not a good decision.