Live data from Hacker News

Rails vs. Django

news.ycombinator.com

31–35 of 35 posts

Re: Rails vs. Django

#31
post #22
post #18

Earlier quoted context omitted.

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…

Things I learnt, that might help. 1. You don't have to use SQL. 2. If you are going to use SQL, Find a wrapper that is minimalistic for your current needs. Work with lesser and you will work more but you will also work with more freedom and sanity. Best of luck friend. :)

Thanks for your thought-provoking comments, actually I had quite forgotten that I didn't necessarily need SQL (despite reading all the threads about that here)!

Trouble is, I understand the theory of in-memory data logged to disk, but as I'm just a humble hacker (self-taught amateur) there seem a lot of unknowns in such an approach. SQL, though a pain, is at least familiar and abundantly documented.

Guess I'll do a little more research, and a little more hacking, since I would be quite happy to drop SQL entirely!

Re: Rails vs. Django

#32
post #19
post #15

Earlier quoted context omitted.

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.

That's right.. in a way.

You need to love the platform you're going to develop on top of. Guys like him, that ask which one is better, needs to at least give both of them a try and see which one he likes it the most.

Just like the most common comments from the Rails vs Django: it's up to which one you're comfortable/love.

I tried Rails, Django, TurboGears and I ended up with ASP.NET.

Re: Rails vs. Django

#33
post #31
post #22

Earlier quoted context omitted.

Things I learnt, that might help. 1. You don't have to use SQL. 2. If you are going to use SQL, Find a wrapper that is minimalistic for your current needs. Work with lesser and you will work more but you will also work with more freedom and sanity. Best of luck friend. :)

Thanks for your thought-provoking comments, actually I had quite forgotten that I didn't necessarily need SQL (despite reading all the threads about that here)! Trouble is, I understand the theory of in-memory data logged to disk, but as I'm just a humble hacker (self-taught amateur) there seem a lot of unknowns in such an approach. SQL, though a pain, is at least familiar and abundantly documented. Guess I'll do a l…

Actually, I am self taught too and most hackers here are probably much better than me. I use python, if you do the same then try out Zope DB and schevo.org. These are Object based DBMS - non SQL. The problem like someone pointed out is that such systems are not language agnostic.

Re: Rails vs. Django

#34
post #29
post #8

Earlier quoted context omitted.

I went for rails myself, and agree about Mongrel. It seems like the Rails guys are all anxious to throw the Apache baby out with the bathwater, and spend a lot of time fooling around with dodgy ways of doing things. For now, I use the mod_fcgid Apache module, and it seems to work ok for what I need.

i heard through the grapevine that zed shaw, the dude who wrote mongrel, is down on it and isn't actively developing it anymore. hopefully someone else will pick up the slack, but i'm afraid that 95% of the folks using ruby+rails are know-nothing newbies (like me). =P anyone have any experience with lighttpd + rails?

Oh really? Why don't you either stop spreading FUD, or back up that statement with some reality. "heard through the grapevine" - give me a break.

Re: Rails vs. Django

#35
post #29
post #8

Earlier quoted context omitted.

I went for rails myself, and agree about Mongrel. It seems like the Rails guys are all anxious to throw the Apache baby out with the bathwater, and spend a lot of time fooling around with dodgy ways of doing things. For now, I use the mod_fcgid Apache module, and it seems to work ok for what I need.

i heard through the grapevine that zed shaw, the dude who wrote mongrel, is down on it and isn't actively developing it anymore. hopefully someone else will pick up the slack, but i'm afraid that 95% of the folks using ruby+rails are know-nothing newbies (like me). =P anyone have any experience with lighttpd + rails?

Wow, in light of recent Zed events, I think I owe you an apology! That must be one heck of a grapevine.
Post reply on HN