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

Rails vs. Django

news.ycombinator.com

Post reply on HN
Print view View original

11–20 of 35 posts

Re: Rails vs. Django

#11

Post by kashif »

dood wrote: post #9

Pylons is deserving of attention. There is a small comparison of Django and Pylons here [ http://wiki.pylonshq.com/display/pylonscookbook/Concepts+of+... ]. I'm playing around with Pylons and have been impressed so far. The whole approach strikes me as more of a hackers framework; less magic, more flexible, extensible. Though the docs need a little work, and the community isn't as big as Django yet, Pylons seems to b…

You are on the money dude, I have been using pylons for a while and it is much more usable than Django.

Re: Rails vs. Django

#13

Post by kashif »

hsiung wrote: post #2

jesusphreak has a pretty good writeup that's worth reading on the pros of using django: http://jesusphreak.infogami.com/blog/why_django Having come from a rails background and later switching to django I think it comes down to a matter of preference. Django's ORM gets the job done but leaves something to be desired (ugly syntax, no multiple database support, also watch out for implicit cascading deletes!). Conversion…

Actually SQL sucks and hence all wrappers suck too. The over-engineered SQLAlchemy sucks most. If you are python user you should find SQLAlchemy ugly.

As far as frameworks goes, for most deployments(not for all) I would suggest pylons over django.

Mako is very useful.

Re: Rails vs. Django

#14

Post by hello_moto »

kyro, why don't you do this instead:

1) Pick a very easy tutorial for both of them 2) Do them 3) Choose

Framework will only get better each day so if today Rails deployment sucks, tomorrow it'll become better unless the growth is stagnant. Same case with Pylons or Django or the 100000000000000001 python frameworks out there.

Now if you're looking for a job, Rails would be a better choice because the hype marketing has converted a lot of people (they drink the kool-aid straight from the hose).

Re: Rails vs. Django

#15

Post by dood »

hello_moto wrote: post #14

kyro, why don't you do this instead: 1) Pick a very easy tutorial for both of them 2) Do them 3) Choose Framework will only get better each day so if today Rails deployment sucks, tomorrow it'll become better unless the growth is stagnant. Same case with Pylons or Django or the 100000000000000001 python frameworks out there. Now if you're looking for a job, Rails would be a better choice because the hype marketing ha…

I don't think this is a good way to evaluate a framework; tutorials don't necessarily bear much relation to the reality of using the tool.

Re: Rails vs. Django

#16

Post by dood »

kashif wrote: post #13
hsiung wrote: post #2

jesusphreak has a pretty good writeup that's worth reading on the pros of using django: http://jesusphreak.infogami.com/blog/why_django Having come from a rails background and later switching to django I think it comes down to a matter of preference. Django's ORM gets the job done but leaves something to be desired (ugly syntax, no multiple database support, also watch out for implicit cascading deletes!). Conversion…

Actually SQL sucks and hence all wrappers suck too. The over-engineered SQLAlchemy sucks most. If you are python user you should find SQLAlchemy ugly. As far as frameworks goes, for most deployments(not for all) I would suggest pylons over django. Mako is very useful.

I'm curious what you dislike about SQLAlchemy, the ORM, the SQL toolkit, or both?

Re: Rails vs. Django

#17

Post by kashif »

dood wrote: post #16
kashif wrote: post #13

Earlier quoted context omitted.

Actually SQL sucks and hence all wrappers suck too. The over-engineered SQLAlchemy sucks most. If you are python user you should find SQLAlchemy ugly. As far as frameworks goes, for most deployments(not for all) I would suggest pylons over django. Mako is very useful.

I'm curious what you dislike about SQLAlchemy, the ORM, the SQL toolkit, or both?

Both, but the ORM more. I am curious, why do you ask?

Re: Rails vs. Django

#18

Post by dood »

kashif wrote: post #17
dood wrote: post #16

Earlier quoted context omitted.

I'm curious what you dislike about SQLAlchemy, the ORM, the SQL toolkit, or both?

Both, but the ORM more. I am curious, why do you ask?

I've been learning it recently and I'm not sure what to make of it, specifically the ORM component. It certainly has a good reputation as far as ORM's go, but I'm not sure if even a good ORM fits a large, popular, or complex app, or is perhaps more suitable for protoyping and low-traffic uses.

But since SQL is pretty necessary for most web apps, it makes sense to pick some abstraction layer, and as far as I can tell SQLA is best of breed for scripting languages, so I'm trying to work out how to apply it most effectively.

Re: Rails vs. Django

#19

Post by cnu »

dood wrote: post #15
hello_moto wrote: post #14

kyro, why don't you do this instead: 1) Pick a very easy tutorial for both of them 2) Do them 3) Choose Framework will only get better each day so if today Rails deployment sucks, tomorrow it'll become better unless the growth is stagnant. Same case with Pylons or Django or the 100000000000000001 python frameworks out there. Now if you're looking for a job, Rails would be a better choice because the hype marketing ha…

I don't think this is a good way to evaluate a framework; tutorials don't necessarily bear much relation to the reality of using the tool.

Agreed. Most of the frameworks have the 20 minute tutorial which (most of the time) is no way comparable to the type of work we will be doing with it.

Re: Rails vs. Django

#20

Post by menloparkbum »

SwellJoe wrote: post #4

Deployment of Rails sucks. Django is far better thought out, and can be deployed in a very sane manner. A fleet of Mongrels is just an embarrassingly bad way to handle concurrency. "I know, let's write a crappy barely functional web server, spawn a metric ass ton of them, and then balance between them with a proxy. It'll be most leet and super fast! We'll call it a Best Practice. It'll be awesome." In fact, it's frag…

what is the preferred way to deploy django these days?
Post reply on HN