> You'd have to define some metrics to measure on. Bugs per thousand lines of code might be good. Average time to deliver n features might be good. Programmer s

> You'd have to define some metrics to measure on. Bugs per thousand lines of code might be good. Average time to deliver n features might be good. Programmer satisfaction might be another good one, or some kind of measure of how easy it is to hire x programmers. There's tons of these. Any of these might be good. I'm not the one making the claim or choosing the words. I'm asking you what you mean. And does PHP (or jQuery) do worse on any of these? It's not clear to me that it does. > The real reason for choosing PHP or JQuery is you're already experienced in them and don't want to learn something new, or you're working on a legacy project. No, I prefer using jQuery. I have used the newer things too. I know how they work. I work with it daily at $dayjob. I still prefer jQuery. You may think that's crazy and that is completely fine, but please don't insult everyone who disagrees with your preferences.