Re:Technical Papers Every Programmer Should Read at Least Tw...
by imanaccount247 on Saturday December 20, 2014 @06:54PM
(#8778414)
They don't have to suddenly improve, they can learn and improve at a normal pace. Yes, of course they should not use PHP. But simply having them use languages, libraries and frameworks that are written by people who get security won't stop them from writing insecure applications to put into production. They still need to learn to write secure code too.
Re:Technical Papers Every Programmer Should Read at Least Tw...
by hueving on Sunday December 21, 2014 @08:10AM
(#8779659)
>Yes, of course they should not use PHP.
Wow, this is utterly worthless, if not harmful, advice. There is no correlation between choosing PHP for an application with the security of said application. PHP apps are so widely deployed that securing them is a pretty well-known process at this point.
Re:Technical Papers Every Programmer Should Read at Least Tw...
by imanaccount247 on Sunday December 21, 2014 @11:00AM
(#8779996)
Yeah, the constant stream of security holes in PHP because the developers are so bad they actually chased away the only person they had who cared about security is nothing to worry about. You can just dip your app in some magic security sauce and everything will be fine.
a) Hope they suddenly improve, which is probably not going to happen
b) Accept they have limits and encourage them to use systems and frameworks that are hard to screw up on, written people who are good at security?
I note in the Sony hack the only computers that survived basically intact were Macs, not I guess because their owners understood security but because they were well designed and idiot friendly.