I have no experience in Django, but heavy experience with Rails. I've moved to Node for a variety of reasons - but my experience is the following: The level of

I have no experience in Django, but heavy experience with Rails. I've moved to Node for a variety of reasons - but my experience is the following: The level of re-usable code is growing quickly in the node eco-system, but it obviously hasn't matured to the levels of Django/Rails in robustness. Many "out of the box" items that are well tested in these frameworks still require more work or crafting your own home grown solutions. I believe the node approach is where the industry is going over the next 5 years. That said, I would personally do smaller projects in node (to build your skillset and familiarity), while doing larger projects in your speciality unless you have a plethora of time for the project. Then swap out the portfolio mix as you become more skilled in node.