Hacker News new | past | comments | ask | show | jobs | submit login

> "Copying" might just be: check your needed dependencies into your source code tree.

> Managing complexity is important, depending on several hundred things (especially if you don't have control over them) is not managing it.

You're still depending on the thing you checked in. You're just storing it somewhere else.

PS. You can achieve the same thing (frozen dependency tree) with shrinkwrap.




> You're still depending on the thing you checked in. You're just storing it somewhere else.

Yes, since it's checked in it won't change "behind your back" or disappear

You also can add fixes to it


>Yes, since it's checked in it won't change "behind your back" or disappear

It will also not get fixed, when important bugs or security issues are discovered and fixed upstream.

>You also can add fixes to it

Which is called a "fork" which you'll then have to maintain.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: