And I respect PHP very much for that focus. But as soon as you go beyond the very basics, I think the learning curve there is steeper. Rails simply has so many answers to so many questions, and it introduces those answers in a pretty progressive way. You don't even have to learn what SQL injection is if you're using the preferred query methods. You SHOULD learn what that is, but you don't have to to get started. If you don't know what SQL injection is and you use the MySQL db query functions with a string-interpolated query in PHP, well, you're going to be in trouble.
Probably he knows the difference:). But he seems to just try to make a point where there is none. He is making a wrong comparison. Ruby on Rails is a framework and should have classes/methods to handle SQL queries, just like any proper framework. Ruby and PHP are languages and shouldn't do that. If you use a framework in PHP, or even a CMS as WordPress or Drupal, you have classes/methods for doing SQL queries.
Conflating language and Framework (Score:4)
Probably he knows the difference :). But he seems to just try to make a point where there is none. He is making a wrong comparison. Ruby on Rails is a framework and should have classes/methods to handle SQL queries, just like any proper framework. Ruby and PHP are languages and shouldn't do that. If you use a framework in PHP, or even a CMS as WordPress or Drupal, you have classes/methods for doing SQL queries.
Re: (Score:3)
Due to Ruby's extensive support for metaprogramming, Rails ends up being a cross between a language and a framework.