[gozur88]

One thing he said I absolutely agree with - when you're in a crunch situation, either in a startup or a new high-pressure project at BigCo, you don't pick a tool set with which you're not familiar. Even if it looks very nice. You're going to have enough frustration making deadlines without the additional hassle of discovering the warts (and they're always there) of a new language.

Where I work there are always projects that are a little bit under management radar - things that need to be done but don't need to be done in a big hurry. That's the right kind of project to scratch your chin and say "You know, I've never written anything in whitespace."

[dagw]

Someone once gave me the piece of advice that a project should only have one 'difficult' part. If it's a difficult domain problem or a difficult deadline, use an easy language (as in one your already very familiar with). If it's an easy domain problem and an easy deadline, then feel free to use a difficult language or framework (meaning one that you'll have to learn while you're doing the project.)