News for hackers. Stuff that matters.
Re:Switch to another language in the middle of a project? by swombat on Wednesday May 21, 2008 @04:17AM (#195830)
I was in almost the same situation as you, and I decided, for the very reasonable reasons explained in the other responses, to stay with PHP.

In summary:

- I know PHP, don't know Rails

- I could be a victim of the "grass is greener" effect

- I'm already too far into the project to make such a drastic change

- I made the decision to use PHP in the first place - I'd look like an idiot for making such a big mistake (even to just myself and my business partner) And so on.

All very good reasons, and I still think my decision was highly defensible, and I stand by it.

However, it was a mistake - the deadly kind. There's no telling what could have happened if I'd switched to Rails at the time (I had a strong hunch that Rails was way better). But here's what happened:

- Turns out we weren't so far into the project after all (a typical mistake) - it was another 8 months before we released

- I've since learned Rails, and reckon I could probably have redone the whole site in less time than that with Rails (probably 3-5 months with better functionality as a result)

- PHP and the framework I used (custom) were not adequate for our long-term aims. The viscosity ( http://www.inter-sections.net/2007/12/01/comparing-pieces-of... ) of the whole thing increased to the point where after we finally went live, making further changes was too expensive/difficult/error-prone to be worth our while

Basically, this decision killed this product that I spent about a year working on.

I still stand by it, but I've learned from my mistake. I even wrote an article about it (though I didn't mention this specific product, the argument applies): http://www.inter-sections.net/2008/01/22/fundamental-mistake...

What would I have done differently? How about take a 2 week break and give Rails a really good try to see how well I liked it and if it was just an impression. I would then probably have made the decision to switch, and I believe it would have been the right one. I suggest you do the same with your product. Building a product that's painful to evolve is a deadlier mistake than wasting a bit of work. Also, it's not all wasted - you've still learnt about the business domain.

Anyway, good luck!

Daniel

There are no comments on this comment yet.