As with any tool, the choice of language should be more dependent on the the job at hand.
A lot of the work that I do can not be done with C#, Java, php, it has to be done with C/C++; then some of it is more appropriate for C#. So first, you have to decide what sort of programming you want to do, then look at what is best to learn to achieve it.
xoreaxeax wrote: |
---|
It is the programmer, that matters, not the language. |
They both matter (and the knowledge of the problem domain). As an analogy; consider a driver as a programmer, the car as the language and the course as the job at hand.
So for drivers and cars we can have Lewis Hamilton driving a Mini and Jenson Button driving an F1 car.
Let's consider, as the course, of 60 laps around Silverstone. The drivers are of similar ability and both have a good knowledge of the track (problem domain). The F1 car will is all likelihood be win.
Now if the course is changed to a trip across London; again they have similar ability and knowledge of London but in all likelihood the Mini will get across London first.
So let's change things a bit in the last scenario, instead of Button we will have a London Taxi driver in a mini. Hamilton is a better driver, the cars are the same but the taxi driver will most likely win because he has a better knowledge of the problem domain.
So to recap, The programmer, the knowledge of the problem domain, and the choice of language are ALL important to the successful outcome of a project.