Simple question: why code it in nodejs if .net core is more than capable of running it?

Because that's how Claude decided to handle it.

Packaging tools for language/ecosystem X written in another language Y are always a red flag. They had to reinvent a bunch of wheels, such as parsing metadata, and they probably did it badly.

See also: uv.

▲

seabrookmx 5 days ago | parent | next [-]

Except uv is by far the best UX for Python package management out there. There's a reason they chose Rust to write this tool.

The same goes for typing.. mypy (written in Python, and contributed to by Guido himself) performed so poorly that they had to invent a bespoke compiler for it (mypyc). The other options written in Rust or node are much more performant.

Another example: the golang port of the Typescript compiler.

I agree with the take it's odd to write a nuget server in node, but the comparison to uv isn't fair. There's concrete reasons to choose a more performant language for the task.

▲

loic-sharma 5 days ago | parent | prev | next [-]

FWIW, the NuGet package format and the v3 server protocol are fairly simple and well documented.

▲

oaiey 5 days ago | parent | prev | next [-]

And so unnecessary. .NET is perfectly fine for that.

▲

whatevaa 5 days ago | parent | prev [-]

UV is different because python performance is dogshit when actual processing is involved. Most fast Python stuff is in C extensions so Rust is no surprise here.

	▲	Kwpolska 4 days ago \| parent [-]
		It would make a lot of sense to do the slow parts in C or Rust. But the only significant slow operation in a package manager is dependency resolution.