News for hackers. Stuff that matters.
Re:The state of Django and Ruby on Rails - one year later by bhauer on Tuesday August 13, 2013 @05:35PM (#6208402)
Great writeup, fallenhitokiri. A shame it didn't see more upvotes when you posted it to get some attention on the home page.
Re:The state of Django and Ruby on Rails - one year later by fallenhitokiri on Thursday August 15, 2013 @01:24AM (#6216316)
Thanks :) even if it didn't make on the frontpage I already received two mails from "just starting out developers" who found it useful, so I'm satisfied :)
Re:The state of Django and Ruby on Rails - one year later by targusman on Tuesday August 13, 2013 @01:32PM (#6207023)
I migth not like Django, but its security is 100x better than Rails. Django fixes stuff right away, and doesn't have any stupid Yaml.load() bullshit.
Re:The state of Django and Ruby on Rails - one year later by fallenhitokiri on Tuesday August 13, 2013 @01:46PM (#6207090)
I'm not sure if Djangos YAML-serializer was effected by this bug but TastiePie did (IIRC) use `load` instead of `safe_load` and suffered the exact same issue e.x.

You could argue that, no matter how prominent a library is, it does not reflect the actual framework. While this is true people could start arguing that Rails doesn't really have an admin interface and this would change the comparison I did.