More as people who value simplicity and hackability.
Like if you use C# you obviously value structure and organization over many other things and aren't afraid of spending money, so deploying everything on your inhouse Kubernetes cluster makes perfect sense. If you use JavaScript you probably have some kind of compile step, and after deploying you need to somehow restart node anyways; Docker makes this easier and more reliable. But if you use PHP the relative advantage of Docker over rsync isn't nearly as big, but Docker adds a lot of incidental complexity.
And if you are small enough you probably want some kind of serverless hosting. With most languages that involves running a tool that creates a docker image and uploads it to that provider. PHP invented that a couple decades earlier and called it shared hosting. It's not as cool and has worse versioning, but functionally it fulfills the same purpose. It just happens to predate docker.
Visual Studio used to be basically mandatory for developing C# and costs $500 per year per developer or more (unless you are happy violating the license of the community edition). Paying for libraries is also completely normal in the C# ecosystem, it's easy to pay another couple thousand per developer for library licenses.
I think you tend to get good value for your money, developer salaries are expensive after all. But for any other language (maybe besides C/C++) this is much less common and the paid products that do exist are much cheaper.
How does this relate to docker? Only really in combination with the other attributes. Rsyncing files into production isn't as traceable, organized, structured or auditable as many of the Docker-based solutions out there. Those solutions can get expensive at scale, but if you use C# you are used to that
Hence the "used to". Both became options 8 years ago and took a bit to mature. Before 2016 everyone had Visual Studio licenses and on top of that got JetBrain's VS extensions.
Like if you use C# you obviously value structure and organization over many other things and aren't afraid of spending money, so deploying everything on your inhouse Kubernetes cluster makes perfect sense. If you use JavaScript you probably have some kind of compile step, and after deploying you need to somehow restart node anyways; Docker makes this easier and more reliable. But if you use PHP the relative advantage of Docker over rsync isn't nearly as big, but Docker adds a lot of incidental complexity.
And if you are small enough you probably want some kind of serverless hosting. With most languages that involves running a tool that creates a docker image and uploads it to that provider. PHP invented that a couple decades earlier and called it shared hosting. It's not as cool and has worse versioning, but functionally it fulfills the same purpose. It just happens to predate docker.