I've used quite a few languages and even though I see the flaws I just shrug and get on with the job at hand, re-writing something because a code base is not written in 'your' language is the mark of a pretty inflexible programmer.
A language snob is someone who derives a feeling of superiority from the language they use, in reality the tools matter a lot less than language snobs will have you believe.
I've worked with lots of people over the years, and some of them were all-out snobs about 'their' chosen language.
These people were extremely irritating to work with because they refused to look past the minimal advantage that you derive from working in language a,b or c.
The stuff most of us create could be implemented in just about any language without anything close to the kind of 'slowing down' that you allude to, it all boils down to how well you know your language and the environment you operate in, as well as knowledge about the domain you are building your work for.
In my experience the choice of language has a relatively small impact on the speed of the initial build and the quality of that build.
Over a longer term for less than rocket science style projects it is far more important to have good documentation and a supply of reasonably competent coders than that it is important to do your project in any one specific language.
Of course, there are languages such as brainfuck and a bunch of others that you'd do well to avoid for many reasons but I take it we're limiting the discussion to the top 10 languages used to build everyday applications and web-apps, say Java, C++, Python, Perl, PHP, Ruby, C# and whichever won't spring to mind at the moment.
A language snob is someone who derives a feeling of superiority from the language they use, in reality the tools matter a lot less than language snobs will have you believe.
I've worked with lots of people over the years, and some of them were all-out snobs about 'their' chosen language.
These people were extremely irritating to work with because they refused to look past the minimal advantage that you derive from working in language a,b or c.
The stuff most of us create could be implemented in just about any language without anything close to the kind of 'slowing down' that you allude to, it all boils down to how well you know your language and the environment you operate in, as well as knowledge about the domain you are building your work for.
In my experience the choice of language has a relatively small impact on the speed of the initial build and the quality of that build.
Over a longer term for less than rocket science style projects it is far more important to have good documentation and a supply of reasonably competent coders than that it is important to do your project in any one specific language.
Of course, there are languages such as brainfuck and a bunch of others that you'd do well to avoid for many reasons but I take it we're limiting the discussion to the top 10 languages used to build everyday applications and web-apps, say Java, C++, Python, Perl, PHP, Ruby, C# and whichever won't spring to mind at the moment.