I'm working in production projects across all 3 languages now and Java and Go are way behind when it comes to producing a polished product as quickly as possible.
There are currently 244,641 libraries through nuget
https://www.nuget.org/packages
Ps. You can use libraries from f#, c# and VB.net. So as a .net developer, your statement doesn't make any sense.
You could have mentioned the different frameworks. But there is interop through the CLR between languages.
The parent post is correct that the third-party ecosystem (especially OSS) is sorely lacking in quality.
Like look at logging - logging in .net is SO anemic. Even with third-party libs, there are so many features missing that have been in java libs like slf and log4j2 for years, yet we have nothing close in .NET.
Hell, you could just pick a feature from spring and compare to what's available in .NET ecosystem, and you'll be sorely disappointed.
Being able to monitor levels via an administrative endpoint.
A decent rolling file implementation that can compress the archived files.
These are all things I've had to implement (on top of serilog, no less) in the past year.
log4j2 has these out of the box.
LoggingLevelSwitch?
> Being able to monitor levels via an administrative endpoint.
I wrote actuator endpoints for this one, was not hard but yeah.
> A decent rolling file implementation that can compress the archived files.
serilog-sinks-file has FileLifecycleHooks?. There's OOB serilog-sinks-file-gzip but you can also implement your own.
All the sinks for whatever you want.
Java simply has developer mindshare, the .Net developer stereotype is so rigid and engrossed that the pay difference between a .Net dev and their Java peer is usually around 20% if not more.
I don't see how this is a valid comparison. Java being paid better has nothing to do with scarcity of expertise.
Whether that explains part or most or all of Java dev pay premium is at least debatable. For instance, I would never make the same "throw a rock into a crowd" statement about finding a competent (but not expert) java developer. That alone means I would expect to pay some of a premium for finding them in that crowd.
What's the counter argument to scarcity? Alignment with better paying industries, weighted so heavily in that direction that it shows up as a premium for their developers? I mean, if you start getting into the conversations about the obscurity of domains, or supplemental education associated with Java developers either by coincidence or requirement, or general demand, I think you're still commenting about scarcity.
JavaWorld is bigger and Java developer count exceeds .net developer count, so the whole scarcity thing is a static explanation of a much complex dynamic environment. The intent here is not to complain about .net dev wages.