PHP vs Ruby (As well as Python and others)
Posted 4 months ago at 1:09 pm. 7 comments
Today I found a pretty cool blog post discussing PHP vs Ruby performance. A lot of people in the web community are suggesting that Rails is slow and it doesn’t scale. A lot of these people making these accusations happen to be PHP people, and so in suggesting Rails is slow and cannot scale they are in essence suggesting that PHP can.
In the article they benchmark PHP vs Ruby, as well as Python, Perl, and C++ for comparison. It’s important to see the distinction between Rails and Ruby. I work at a Python development house (rockin’ Django) and it’s cool to see all this crap hitting the fan all over the interwebs from Rails. Ruby itself is a great language. It’s also cool to see Python, the little quiet guy in the corner of those charts, smoking the pants off of everyone with the exception of C++. With Psyco (a Python JIT compiler) Python was even quicker than C++.
Check out the post here.
This is awesome — very cool to see the five back-to-back like this. I’m still a PHP man, but Python is looking better and better (I know that’ll make you happy ^^). Might have to start down that path, hmm?
“Rails performed much better than Symfony. And Django performed much better than Rails.” :)
I am just starting to learn Ruby On Rails. I’ve been using php for the last few years. The only problem I have with it is implementaion. Can people really make a whole customizable site with Ruby On Rails? It seems like a bunch of preset layouts to me, and then you customize ontop of that. Am I wrong? What is Django? Is that a better choice than RoR?
Wo wo wo, Wildwobby don’t speak if you don’t understand Rails fully. From the 3 tutorials you have looked at, writers like to make Rails look like a whole pre-build scaffolding system. It’s not. In fact they took out quick scaffolding implementation in 2.0. Check this book out, http://media.sitepoint.com/books/ror.pdf . It’ll get you started.
the link doesn’t work Levi.
Ineffective test. PHP runs as an Apache module so that it doesn’t have to restart the engine everytime. After EVERY run of the script, the engine shuts down (rather than staying up and running in the background like all the others). In it’s natural environment (ie it is a WEB LANGUAGE), it runs as an apache module and would stay up and running constantly and would HALF it’s processing time.
This with the fact that as the requests scale up, RUBY require incrementally more processing power to where RUBY actually tops out and PHP, PERL, PYTHON and the others can actually continue to scale upwards.