4 ms·
kyro, why don't you do this instead: 1) Pick a very easy tutorial for both of them 2) Do them 3) Choose Framework will only get better each day so if today Ra
by hello_moto 19y ago
kyro, why don't you do this instead:
1) Pick a very easy tutorial for both of them
2) Do them
3) Choose
Framework will only get better each day so if today Rails deployment sucks, tomorrow it'll become better unless the growth is stagnant. Same case with Pylons or Django or the 100000000000000001 python frameworks out there.
Now if you're looking for a job, Rails would be a better choice because the hype marketing has converted a lot of people (they drink the kool-aid straight from the hose).
- dood 19y agoI don't think this is a good way to evaluate a framework; tutorials don't necessarily bear much relation to the reality of using the tool.
- cnu 19y agoAgreed. Most of the frameworks have the 20 minute tutorial which (most of the time) is no way comparable to the type of work we will be doing with it.
- hello_moto 19y agoThat's right.. in a way. You need to love the platform you're going to develop on top of. Guys like him, that ask which one is better, needs to at least give both of them a try and see which one he likes it the most. Just like the most common comments from the Rails vs Django: it's up to which one you're comfortable/love. I tried Rails, Django, TurboGears and I ended up with ASP.NET.