That explanation is technically true but it&#x27;s like blaming human error for factory workers being injured by a machine without safety guards. Since it happens so frequently you have to ask how the language could change to make it less common.<p>Most of it comes down to being developed ad-hoc with convenience for solving a simple problem right now as the main driving force.<p>Remember register globals? That was a minor convenience which took ages and millions of exploits to be removed – I remember lobbying for that in the late 90s.<p>Similarly, you mentioned SQL injection. Unlikely as this may seem now, there was a time when things like prepared statements were an exotic new feature with limited library support and a certain school of programmer thought they were probably too slow. The docs and most tutorials didn&#x27;t mention things like validation or escaping prominently so most PHP developers were trained to slop everything into strings. When PDO came along, this persisted for too long as well and even after they started recommending placeholders you didn&#x27;t get something like all of the mysql functions saying “Don&#x27;t use this, it&#x27;s unsafe”. I&#x27;ve heard that this has improved but it&#x27;s been years since I needed to look.<p>Similarly, look at the lax attitudes toward error handling — errors are ignored by default, database errors or warnings have to be explicitly requested, etc. That&#x27;s “easier”, saving whole seconds of learning at the expense of millions of successful exploits and hours spent debugging.