Java itself was a much slower standard workflow. Dynamic languages in general, like Ruby, Python, Perl or PHP were much faster to work with than the burdensome recompile workflows. Think instant feedback vs waiting for your CI to finish after every single save. The speed of iteration was critical.
Beyond that, when the speed of development is slower, more people get hired to do the work. When more people get hired to do the work, there's more communication relay as the team size grows. Teams coordinating between each other. Decisions going to committees. Middle management layers.
You'd routinely see companies with 3-5 Rails devs outperforming shops with 50 Java devs. Communication and iteration speed was huge. The other piece of it was the convention over configuration aspect because it removed so many things you'd have to discuss and make decisions about as a group which further accelerated communications.
10-20x multiplier isn't an exaggeration at all. If anything I could be underselling it.
On one extreme, a solo dev could prompt a frontier SOTA agent with not much more than "Build Uber", give it the necessary hardware/software/permissions to build itself a useful feedback loop and act autonomously, put it in goal mode, and let it cook, and as long as the tokens kept flowing they'd eventually end up with something reasonable in actual orders of magnitude less time than it would have taken that dev to build the same thing — especially if you're counting calendar days rather than hours worked, and extra especially if they wouldn't have had the luxury of investing full-time hours into that particular thing. At the opposite extreme, BigCo full-time SWE #5000 tasked with an extremely specific ticket for a critical revenue-generating brownfield system might experience even "20%" as liberal, and correctly observe that writing code was never the bottleneck for their job. And then there's the massive spectrum of circumstances in between those two ends.
None of that means that the gains aren't real, or that anyone in particular is wildly exaggerating in either direction. It just means the gains aren't evenly distributed.
If you're allowed to use the newer libraries and tools, it has actually been a perfectly fine language to write software in, even relatively quickly, since ~Java 8 or 11.
I have had elaborate fantasies of what I would do to the designers of JavaEE if I ever found them, and I had assumed that because writing JavaEE is so unbelievably horrible that the entirety of the platform was like that. Years later I had a different job that was much more amenable to me using "modern" Java, so I used Vert.x and Disruptor and properly learned how to use NIO and and I actually had fun.
I think Java has been the "regression to the mean" language primarily because it's taught to frequently in schools and it allows you to write in a very verbose and irritating style, meaning that it was a great fit for mediocre-to-incompetent engineers who want to look like they're doing a lot.
sigh