My answer depends on what you mean by “productive.” I can produce the most working code per hour in SQL. I also get paid the most per line of code for SQL. Repl

My answer depends on what you mean by “productive.” I can produce the most working code per hour in SQL. I also get paid the most per line of code for SQL. Replacing 300 lines of application code with 20 lines of SQL gives a net reduction in source code (if that’s what you mean by “output”). I can write working application code fastest in C, meaning the most lines of code per hour. That doesn’t necessarily translate to what I call “productive” in the sense of something that solves a business problem and doesn’t incur long-term costs. I can write PHP code very fast too, from years of experience working with legacy PHP projects. I think of “productive” as making the most money for the time I spend. Programming languages have little to do with that measure of productivity.