5 ms·
I just left a rails gig to go back to django. I like ruby ok but not a big fan of rails. I totally see the value and understand why someone would like it but I
by mehphp 5y ago
I just left a rails gig to go back to django. I like ruby ok but not a big fan of rails.
I totally see the value and understand why someone would like it but I just never could get to that point with it.
I much prefer the explicit imports, loops, etc I suppose
- chespinoza 5y agoThat's interesting, what you think Django excels that Rails doesn't? Which ones were the pain points in your opinion?
- mehphp 5y agoI think it’s just preference really. I don’t think Django is better I just prefer some of it’s choices. For example, I really don’t like that rails implicitly imports stuff into the namespace. I like being able to follow the imports explicitly at the top of the file. I feel like there is way less of “where does this come from or what IS this?” when working with Django.
- t-writescode 5y agoAutoloading is a major source of pain in Ruby, I think. What function did I import, exactly? Which of the 37 “update” calls did I call when I called it on this?