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.
Part of why I'm so productive, I think, is that I trust the type system to "catch me"; I make a change in the most obvious way I can think of, and then see what the downstream effects are by looking at which callsites and expressions I've broken, according to the compiler. I don't have to think through every implication of every change, so my brainpower is saved for more complex things like reasoning about async control flow or thinking about performance.
I feel particularly productive in Python and R but I think I write my best code in Go, C#, or Elixir