Ask HN: PHP vs Rails
I have a project built in PHP (and CodeIgniter) and it's ready to release. It's based on the Facebook API, so it at least makes sense to write some of it in PHP.
PHP doesn't make me happy though the same way Rails makes me happy and motivated to code. I was thinking about this today when I read this about Ruby:
"Yukihiro Matsumoto (a.k.a. Matz), creator of Ruby, said that he wanted to minimize his frustration with programming, minimize his effort in programming and have fun with software development."
I knew this, but forgot about it.
What do I do:
1) Release and just stick with PHP. 2) Release and Re-write it down the road. 3) Re-code it in Ruby and push back the release date?
Doing any re-coding will be a waste of time and take away from adding new features.
10 comments
[ 6.0 ms ] story [ 42.0 ms ] threadYou might be better asking PHP Vs. Ruby or CakePHP, Zend Frameworks Vs. Rails.
Is it Rails that makes you happy? If so i understand CakePHP to be a rails clone in the PHP language.
If it does have legs then you can justify the time and effort it will take to port it to your favorite new language du jour.
Delaying launching for pointless rewrites is a great way to never get to the point where you will launch it, it means you're in love with the tech, not trying to get off the ground.
If you fall in the middle, then you might have a tough choice to make, but let that time come.
Also, there are still other projects, either after this one is done or as a complimentary service/product to support it. You can use Rails for that.
If you're that close to release, this is a bad stage to rewrite anyway, regardless of language. Second system effect might overpower you, and you waste lots of time to implement features that you don't need (yet).
I've seen this way too often where people seem to think that you need to write in PHP to use Facebook. This is absolutely incorrect and false!
I've shipped a number of Facebook applications that are all in Rails that use the creaky RFacebook gem. Even though it's creaky and old, due to the magic of method_missing, this gem handles all the new Facebook API calls magically without a code change. PHP developers need to wait for Facebook to update their library to get the same support (or update it themselves)
Having said that, since it's written already, and is ready to launch right now, you absolutely must launch it. Right now. If it takes off, you can decide where to deploy your resources later.
Nothing beats shipping product.
I agree that product matters and not technology and I will remember this.
The site is http://tabtrick.com if anyone was interested.
Let's call this a quiet launch (soft launch)
If it's successful, hire someone else to look at the PHP for you.