swiharta

and unfortunately, outdated

This is very similar to Susy for Sass / Compass.

The big benefit for me is not having to revisit the markup to change a class from grid_4 to grid_5 and such. You just leave the markup as is, and all the work to change the layout stays in the style sheets, as it should be.

Got PHP developers? Why not an MVC framework in PHP. Using Wordpress for anything but a blog is a disaster.

I'm pretty sure the project I'm working on will be the next Twitter, and this video's making me second guess staying with RoR.

You clearly haven't used Django in quite some time:

try "pip freeze > requirements.txt" and "pip install -r requirements.txt" for managing dependencies between deployments

deployment is a matter of making a generic .wsgi file and pointing your server to it, how is that hard?

the "south" app makes database migrations very easy, the fact that you didn't know about this speaks volumes about your "experience"

Django is universally known to have better docs than Rails and virtually any other web framework, see almost every comment on this page

Your other comments lack any objectivity and aren't even worth responding to. I have nothing against Rails, but it's fanboys like you that give it a bad name.

There are in fact more books focused on Rails compared to Django, and this logically reflects the inferior documentation of Rails compared to Django, necessitating and creating a greater market for additional documentation. This market doesn't exist so much for Django not because of the lack of interest in learning Django, but because the documentation is so good. End of that story.

As for the greater perceived online presence of the Rails community, I think this reflects two things:

1) Greater confusion among Rails users, who as a general group seem less technically inclined "on the whole" (there are obviously a ton of brilliant Rails developers as well). In general, Rails users want things to be pre-configured for them, and therefore never really learn how things work under the hood, and are thus ill-equipped to make simple changes to their own apps.

2) Greater Apple-like fanboy-ism among Rails users, which takes on a religious fervor with people thinking they have met salvation, and it makes them feel special. They love to evangalize about it, and this personality trait in part the perceived greater popularity of Rails.

That said, both frameworks are obviously still very popular and effective at building web applications. Try both and go with whichever one you like better, and stop fretting about whether you've made the "right" decision.