How can you help your client to choose the best programming language for their new software project?

• By their needs and requirements
• Cost and resources
• By functions
• By keeping future needs and requirements

it depends on the project requirements, for example has the project a real-time feature ?

Thank you for the question,

I liked the answer of Mr Muhammad Farooq

I agree with colleagues answer

Thank you for the invitation

Thank you for the invitation. Answers of our colleagues have been covered the requirements of the question. The main point, Fully understanding the client's needs and requirements to adopt the best solution in the cost and language.

Thanks for invitation -

Agree with Mr.Muhammed Farook answer  !!!

This question is quite broad but lets break it down into two very broad categories.

1. Infrastructure already in place

When your client comes to you stating that they need work done on an existing platform the options start to feel limited. However, in my experience, you're really not losing out on too many options for solutions (lets not talk about languages). These days multi-stacked (various technologies) have become the norm because saying that you want to use technology X to achieve everything is neither in your clients best interest or your long-term solutioning as most technologies either come with things they can't do or really excel in one space while failing in the other. 

In such scenarios carefully picking your technology based on growth patterns and how your client perceives using the application is more important when talking to your client. You're not going to say I built this site in C# or Java you're going to be talking pure functionality. Your site wants to achieve a particular function and the programming language is a non-discussion point. The bigger worry is the platform you're on and what it can and can't do. 

2. No infrastructure in place

In this scenario you can really pick any technology or stack you want and then it becomes more important for you to assimilate your client's needs and translate them to the tech choices you make. This happens to be the harder of the two because decisions made here have long-term impact on newer processes onboarded or functionality that will require changes down the road. In most enterprise environments, the turn-around time of ~10yrs is where you start to see whether the original decisions were good ones. You can't mitigate that kind of failure and nor would you want to. It's really just a matter of knowing what you want to achieve and making sure that your decisions are right. Read loads, understand architectures, look at market trends and then discuss a solution with your client. '

I hope this helps.

I am wondering why you invoke the client on choosing programing language , I think that the client should concern more about the functionality of the software and the deliverables required to achieve using that software .

By understanding their needs and analysis the software functions and the future versions.

Thank you for the invitation. It actually depends upon the nature of the project. In my view, you should convince them to use a user-friendly programming language.

It depends on the project environment and the available resources skills to deploy the software project.