| Php is a scripting language specifically designed for web development. Hence, not fit to be in a head to head comparison with a general purpose programming language. Thus the comparison is held at that level (web), comparing php with a web framework. If that wouldn't make any sense, then it does make sense to compare php with C++ or Java (which it doesn't).
After all, you can write a website in C++. Putting that aside, your viewpoint is hilarious as well. I find it amusing how you call the issue you linked at, a core rails bug when your knowledge of rails doesn't qualify for such a statement. It wasn't a bug. If you are a rails developer, have indeed read the issue and replies or at least read the title well enough, you would have concluded that it was a bad coding practice. The security measure to prevent such mass attribute assignment "was" present for developer's to utilize.
It's a single line of code, but some lazy asses wanted that auto-generated/forced/opt-out instead of opt-in. It's a good practice, an advised practice, a recommended practice to write that single line of code. The fact that a mass majority of rails developers didn't write it, or ignored this warning doesn't mean it's a "core rails bug". No, the ruby/rails community is not as large as Php. Yes, the php community has an awkward tendency to write "below" the par software while charging for it. Any experienced php developer will confirm this sad fact and will probably blame the language for it (Php "is" flawed on so many levels: http://me.veekun.com/blog/2012/04/09/php-a-fractal-of-bad-de...) |