Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: Updated recommendation on Rails versus Django?

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 39 posts

Re: Ask HN: Updated recommendation on Rails versus Django?

#11

Post by shabda »

AhmadH wrote: post #8

You can't go wrong with any of them. I think Django has a slight edge by having a slower release cycle. I find it a desirable quality in a development framework. While the number of man-months spent developing Rails is an order of magnitude greater than that spent developing Django, is it really that much better for the bottom line? Most of the early efforts spent on Rails were to make the infrastructure and communit…

> While the number of man-months spent developing Rails is an order of magnitude greater than that spent developing Django

Wildly off base figure

1. Years under development. ROR: 5/Django 5

2. Members in largest google group: ROR 18000+/Django 14000+

3. Members in Irc currently: Ror 436/Django 401

4. Commits to repo: Ror ?/Django 11000+

So while Ror has a bigger community, it is not that much bigger.

Re: Ask HN: Updated recommendation on Rails versus Django?

#14

Post by Pypie1 »

shabda wrote: post #12
tptacek wrote: post #4

No offense, but how amazing can your idea be if it allows you to procrastinate on web frameworks?

No offence, but why is evaluating technologies which you are going to be stuck with for a very long time a bad thing?

Agree totally... it's important to ask these sorts of questions early...

Re: Ask HN: Updated recommendation on Rails versus Django?

#16

Post by Pypie1 »

jm4 wrote: post #6

If you've borrowed money from family and friends to hire some developers in order to get something working as quickly as possible you should use whatever tools are going to help you make that happen. You probably don't want to be tinkering around with a new language and framework on top of having to work with developers you're unfamiliar with when you're dealing with a project of this importance. Use what you know. I…

At the same time, if I simply had stuck with what I knew over the years I'd still be doing old ASP...i'd be more miffed as an investor if you had a great idea but killed it because you did it in vbscript just because that is what you knew, or if you chose something that would cost a lot more to scale, thus requiring greater investment just to see a return.

Re: Ask HN: Updated recommendation on Rails versus Django?

#17

Post by carbon8 »

Pypie1 wrote: post #13

What about performance and scalability? Doesn't python (with psyco and soon, unladen swallow) win big here? When you choose a platform, it's important to choose one that won't limit you when you start having users on a large scale...

Unless something changed, django doesn't even run on psyco cleanly and the combo is unsuitable for production. Unladen swallow also isn't ready for use in production with django and it's unclear when it will be. But performance from these languages aren't the bottlenecks in web apps, and Ruby 1.9 and Python 3 have similar performance, anyway.

Re: Ask HN: Updated recommendation on Rails versus Django?

#18

Post by carbon8 »

Pypie1 wrote: post #16
jm4 wrote: post #6

If you've borrowed money from family and friends to hire some developers in order to get something working as quickly as possible you should use whatever tools are going to help you make that happen. You probably don't want to be tinkering around with a new language and framework on top of having to work with developers you're unfamiliar with when you're dealing with a project of this importance. Use what you know. I…

At the same time, if I simply had stuck with what I knew over the years I'd still be doing old ASP...i'd be more miffed as an investor if you had a great idea but killed it because you did it in vbscript just because that is what you knew, or if you chose something that would cost a lot more to scale, thus requiring greater investment just to see a return.

That might be relevant if we weren't talking about modern and very actively developed web frameworks on modern and quickly evolving languages.

Re: Ask HN: Updated recommendation on Rails versus Django?

#19

Post by mechanical_fish »

shabda wrote: post #12
tptacek wrote: post #4

No offense, but how amazing can your idea be if it allows you to procrastinate on web frameworks?

No offence, but why is evaluating technologies which you are going to be stuck with for a very long time a bad thing?

Because, in all likelihood, worrying that you're going to be stuck with your initial choice of technology for a very long time is premature optimization. You should be so lucky.

I have no idea what the original submitter's idea is, but I'll still predict how it's going to work out: It won't find product-market fit. So it won't need to be maintained for a very long time. So he might as well just build it with the framework he already knows, get it over with, and move on to the next idea.

Anyone want to bet that I'm wrong? If so, please make out your angel checks to the original submitter.

Moreover, while fretting too much about the apparent greenness of the grass on the other side of the fence is always a warning sign of procrastination, doing so when you already have three years of Rails experience and know exactly where its pain points are is really a sign of procrastination. Just build the thing already! You will save time by working in a framework that you already understand. And, if you like, you can use that saved time to improve the bits of the framework that you dislike.

Re: Ask HN: Updated recommendation on Rails versus Django?

#20

Post by plinkplonk »

mechanical_fish wrote: post #19
shabda wrote: post #12

Earlier quoted context omitted.

No offence, but why is evaluating technologies which you are going to be stuck with for a very long time a bad thing?

Because, in all likelihood, worrying that you're going to be stuck with your initial choice of technology for a very long time is premature optimization. You should be so lucky. I have no idea what the original submitter's idea is, but I'll still predict how it's going to work out: It won't find product-market fit. So it won't need to be maintained for a very long time. So he might as well just build it with the fram…

I'll just the change the ending of what mechanical_fish said,

"i have no idea what the original submitter's idea is, but I'll still predict how it's going to work out: It won't find product-market fit. So it won't need to be maintained for a very long time. So he might as well just build it with the framework he "

doesn't know and learn something interesting along the way. It won't take him much time to be fluent in Django if he is as conversant with Rails as he claims.

But yeah it really doesn't matter whether he uses Django or Rails. mechanical_fish's larger point is still very valid.

I agree with "Just build the thing already!"

Post reply on HN