Is this a win for .NET where the mothership provides almost all what you need?

benbristow a day ago | parent | next [-]

.NET is great because you use a FOSS library and then a month later the developer changes the licence and forces you to either pay a subscription for future upgrades or swap it out.

▲

cylemons a day ago | parent [-]

Yeah why is this so common in .NET?

	▲	benbristow a day ago \| parent [-]
		Enterprise usage. Devs know companies will just pay out. Easier than trying to get sponsored.

▲

koyote 18 hours ago | parent | prev | next [-]

Definitely!

The amount of third-party (non-testing related) dependencies needed for most .NET applications is very manageable and the dependencies themselves (generally) don't come with further third-party dependencies (especially now that JSON serialisation is native).

This means that for most applications, the developers know exactly which dependencies are needed (and they are not hidden away in large folder structures either, the dlls are right next to the assembly).

▲

raincole 2 days ago | parent | prev [-]

C#/.NET is a good example showing no matter how much programmers you have, how much capital you hold, it's still impossible to make a 'batteries-included' ecosystems because the real world is simply too vast.

▲

iamkeithmccoy 2 days ago | parent [-]

Say what you want but I can write a production backend without any non-Microsoft dependencies. Everything from db and ORM to HTTP pipeline/middleware to json serialization to auth to advanced logging (OTel). Yes, sometimes we opt for 3rd party packages for advanced scenarios but those are few and far between, as opposed to npm/js where the standard library is small and there is little OOTB tooling and your choices are to reinvent a complex wheel or depend on a package that can be exploited. I argue the .NET model is winning the new development ecosystem.

	▲	Adachi91 a day ago \| parent \| next [-]
		I agree with you, almost all .NET code I write is within the .NET framework, yet when I look at C# repos, it's disheartening to see so many (new) projects just NuGet this NuGet that. We have text.json now but I still see people use Newtonsoft JSON. There's old repo's out there that should be archived and deprecated, yet I see new games use it when the repo is very questionable with automated whitespace or comment commits to keep up the appearance that it is still being maintained[0]. Right now I'm working on a Golang project and the dependency tree is a nightmare to say the least, I hope to be able to rip out the parts I don't need and compile it without the massive bulk that I do not need. It's very frustrating to want me to trust the author, who trust the author, who trust the author. When I doubt they even audited or looked at what they imported. [0] https://github.com/sta/websocket-sharp
	▲	joquarky 2 days ago \| parent \| prev [-]
		I'm not a fan of that ecosystem, but you make a good point. I wish JS had more basic utilities built in.