Hacker News new | comments | ask | show | jobs | submit login

I do both; they're both worthy of your time to investigate. I've had more success with Django. They both offer roughly the same thing, but when it comes to taking something live and handling significant traffic, I find it's easier to go out of the box with Django. That is, when the plain vanilla is no longer sufficient, Rails, as a matter of course, fights you. I appreciate the "we know better" paradigm that it operates under because it can teach and enforce some pretty good practices. Although I speak only for myself, I've had many conversations with some very experienced folks, and I've felt like we were on the same page.

Also: if you're already comfortable with Cake, the jump to Rails is probably quite short. I'll bet you become very productive on it very quickly.

The Python job market in New York is hot, and Django is very popular. I don't see too much other than Rails opportunities for those that bring Ruby knowledge, but there is certainly enough Rails work to keep you busy. The upside is that there are lots of CMS and infrastructure stuff that is Ruby based, but they tend to be products in their own right rather than tools to hack on. In my opinion, Rails carries Ruby in the market. Without Rails, Ruby would probably fade back into relative obscurity.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: