> This is just an appeal to the law of averages. I don't believe that you're actually considering ada, cobol and forth for new projects. First it greatly depe

> This is just an appeal to the law of averages. I don't believe that you're actually considering ada, cobol and forth for new projects. First it greatly depends on what "new project" mean here. There myriad of new projects within existing code base for which the existing used technologies are the major factor. When it’s about creating a brand new product out of a blank slake, sure Cobol won’t be your first idea for a startup. Maybe Ada might come to mind if some high level of reliability is required, like in aeronautics and the like. It also depends on the team skills. If you have team mates which are all Haskell advanced practioners, surely imposing J2EE for the next big thing might not be brightest move in term of crew motivation.