|
Generally speaking, when you develop a product, you choose the language according to requirements. Any language that can't produce the required performance goes out the window. After that, evaluate the language in terms of rapid development (time to market), maintainability, and support. A neat language that is going to change radically on the next release, deprecating and obsoleting a bunch of things, is probably not a good choice. A language very few people can program in is probably not a good choice. You get the picture. Code available in multiple languages can rarely, if ever, be called a feature.
Any other approach is generally indicative of a toy project, or a person unfamiliar with the realities of profitable production.
|