RoR vs Django

I love Django. It was the first framework I used when I took a new look four years ago at web development after playing around with PHP during my high school years (it was PHP3, almost 4 at the time…). And I developed two projects with Django.

But now I am considering getting a new job with a startup and they already have a website developed by a freelancer using Rails. So I spent the last week going through this book and I have to admit I am impressed.

So impressed that I will probably be using Rails from now on when I do not need to develop single page applications where I believe Meteor has a stronger case.

This is just my opinion but in case you still have a doubt on which framework to go with to get things done quickly, go with Rails.

Meteor: closer to the future of web frameworks

Back in April last year I was writing about my recent discovery of the full stack javascript frameworks, and at the time I was thinking this was maybe going to be the way of the future in web development.

Well almost a year later, I have kept reading articles on these libraries and I have to admit I never really tested anything, and stuck to Django for my web projects.

Until this week where I heard about Meteor from a friend. And now I have to admit that even if I am a little reluctant to fully dive into this new tool due to the lack of a proper debugging for Javascript, I was more than impressed by the features it offers: fully responsive, live update, easy deployment, package system, thriving community, etc…

It will not kill Django and Rails overnight, they keep an edge for the backends, but if you have not already done so, try the demo project: a persistent collaborative todo list.

Some guys even wrote a Trello clone on github.