[dahfizz]

I don't get it.

The git server you use supports artifacts already. You could also just put all of your artifacts on an S3 bucket if you needed somewhere to put them, which is exactly what this is but more expensive. I don't understand when this would save you money or simplify devops.

[cle]

It’s not “exactly what this is”. Every time AWS or Azure or GCP releases a service, there are a droves of people on HN decrying them as “just <something I’m familiar with>”, without bothering to understand if that’s actually true. It’s not.

Skim the docs and you will see it is not “just S3”.

[thayne]

yep. I've worked on a solution that "just uses s3". It is not trivial.

[code4tee]

Can occur in a VPC without direct internet access. For the average developer this isn’t usually an issue but in highly secure corporate environments this helps a lot. Can’t just do pip install X in such situations. Even the S3 proxy solutions often require many hoops from the security Jedi council before you can use any packages there.

A lot of people won’t find this useful but for some it’s a big blessing.

[blaisio]

For python at least, fetching something from git is far slower than fetching it from pypi.

[dmlittle]

The benefit is being able to keep your existing maven/npm/pip workflows as well as use the same workflow for both internal and public dependencies.

[dahfizz]

I still don't see what's different. I can configure pip to look at my git server, so that all I have to do is `pip install my_thing` and it will automatically download all public and private deps. I don't know what you mean by "workflow" in this context but this is just about as simple as can be.

[code4tee]

You’re not the target user here. In highly secure environments you can’t just “pip install your-thing”.

[baq]

Looks like you’re assuming you have some kind of access to any part of the internet you please. I envy you because most tools just work in this case.

Not so on enterprise networks.

[rantwasp]

what git server is that?