Earlier quoted context omitted.
I'd encourage you to read those vulnerabilities, not just Google to disprove me. I'm speaking specifically on the ability for someone to remotely execute code on a ASP.NET WebForms application, and that was just a random example. What you linked to was comparable to saying Groovy is insecure because of the most recent vulnerability found in Java browser plugins. ( http://www.itpro.co.uk/645031/new-java-7-bug-prompts-…
> What you linked to was comparable to saying Groovy is insecure because of the most recent vulnerability found in Java browser plugins. Not really, because in .NET separating the "language" from the "framework" is a little thornier. And the difference is all the more moot from a practical point of view: you still have to rush out and patch everything. > However, when we get to a point where most apps are in framewor…
Possibly 2-3 people have read it who know their shit. The rest are just consumers.
Frameworks only centralise the security concerns - they don't necessarily make it better. That is in the hands of the implementor and their ability to build bullet proof abstractions. One fuck up and your system is globally compromised. It is the right solution, but you need the right people. Rails hasn't had the right people.