How large a project do you typically use dotnet for?

IME dotnet dependency situation is a tire fire, not a month goes by without another dependency biting the dust or going fully commercial with no notice. Which is fair, I suppose, but Go and Java ecosystems don't have it nearly as bad.

▲

orphea an hour ago | parent | next [-]

I don't think going commercial has been that impactful. It sucks, it betrays the spirit of open source but whatever. A few examples:

- FluentAssertions had no moat, and it has been forked as AwesomeAssertions. Not sure what the author's play was here.

- Moq lost trust - we have NSubstitute

- AutoMapper and MediatR have been widely misused anyway

- Maybe MassTransit is a real bummer?

	▲	Pay08 26 minutes ago \| parent [-]
		Switching to the forks/alternatives is still time and effort, often a lot of it.

▲

bob1029 35 minutes ago | parent | prev [-]

> How large a project do you typically use dotnet for?

The largest dotnet project I am responsible for has around 50 megabytes of source files sitting on its main branch right now. If you include the generated WCF references it's probably closer to 100 megabytes.