Switch to another language in the middle of a project?

I've said this a lot, but I can't recommend Code Igniter enough when working with PHP. Quite fast, almost feels like an entirely different "real" language with so much library support from the framework.

Even when I work with Django (being a huge Python man myself), I miss having some of the better aspects of Code Igniter (and definitely CI's user guide is stellar).

Don't switch languages mid-way unless you have a great reason. PHP blog-flak isn't a good enough reason (IMHO) unless your team is fluent in another language they can code more securely.

Thanks. We already use PHPTAL. Will Code Igniter work with PHPTAL?

The answer depends on the purpose of the project. If you're building something to make money, you should not spend the time now to switch languages unless your NEW language has some library or feature which your current project simply cannot work without. However, if this is a learning exercise only or just a fun project, there would be no harm in spending the time to explore both the Python and Ruby options.

The key to your decision here should be how much time and effort it would require to duplicate a feature you want to use in your existing system as compared to what comes out of the box with either a new language or an existing PHP framework. If it's a pain to do and the functionality is critical to your project's success, then you should port. Otherwise, I'd recommend you keep doing what you're doing.

I think the answer kind of depends on the nature of the project.

Re-writing something you have now in another language/framework can be (in addition to fun) a great way to learn the new language/framework. If this is just a fun project, well, cool - best of luck to you. If this is a business, something that you'd like to start making money (or at least getting press) from, then maybe the delay will hurt you more than the fun will help you.

In my case, the website was the online component of a small university department. I inherited a PHP codebase that worked, but that I really didn't like, and opted to re-write it in Python/Django. I'm really happy with the decision: I think it was a great way to learn the framework, and the result is a lot better than the PHP site that it replaced, but I don't think I would have done it if I hadn't had a working PHP site to placate students while I was working on it.

Good luck with whatever route you choose to go.

interesting point - when you have it majority of components ready-made for you, are you really as disciplined a programmer? im going to say "yes," on the assumption that you had the self-control to go to the hardware store and buy a hammer instead of making a set of tools to make a hammer, as the metaphor goes.