4 ms·
the original post was not very pertinent anyway, as far as ruby/rails is concerned. All 7 reasons have almost nothing to do with ruby/rails: #1 - "is there any
by matstc 19y ago
the original post was not very pertinent anyway, as far as ruby/rails is concerned. All 7 reasons have almost nothing to do with ruby/rails:
#1 - "is there anything rails/ruby can do that php can't do? ... (thinking)... no."
#2 - our entire company's stuff was in php: don't underestimate integration
#3 - don't want what i don't need
#4 - it's small and fast
#5 - it's built to my tastes
#6 - i love sql
#7 - programming languages are like girlfriends: the new one is better because you are better
- neilk 19y agoHe lost me at #1. Technically, there's so many things Rails and Ruby can do that PHP can't. If he means it pragmatically (they're both data/web connect-o-thingies), then he has a point.
- Jd 19y ago<<So many things Rails and Ruby can do that PHP can't>> Meta-programming? What else? Do you mean the language or accompanying libraries?
- drm237 19y agoIt's interesting that no one has a problem comparing a Framework to a straight-up language. You'll never get an accurate comparison this way and I think that's a huge point. Everyone marvels at what RoR can achieve in terms of logic/decision/data/presentation separation, but doesn't take into account that there are probably 20 or so PHP frameworks that also implement the MVC approach and do a lot of the same things while maintaining the flexibility of php.
- spiralhead 19y agoArguably, Ruby does things better/lighter/cleaner/more elegantly than PHP, but at the end of the day, they're both accomplishing the same business objective. And when the end result is the same, what PHP provides in the way of stability/industry uptake/user community/compatibility outweighs whatever gains in "programmer happiness" and all the other intangibles commonly flailed about by the Ruby/Rails community.