this post was submitted on 14 May 2025
322 points (99.4% liked)
Programming
20182 readers
215 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Quite frankly, companies shouldn't be pulling Willy nilly from github or npm, etc anyway. It's trivial to set up something to cache repos or artifacts, etc. Plus it guards against being down when github is down, etc.
It's easy to set up a cache, but what's hard is convincing your devs to use it.
Mainly because, well, it generally works without configuring the cache in your build pipeline, as you'll almost always need some solution for accessing the internet anyways.
But there's other reasons, too. You need authentication or a VPN for accessing a cache like that. Authentications means you have to deal with credentials, which is a pain. VPN means it's likely slower than downloading directly from the internet, at least while you're working from home.
Well, and it's also just yet another moving part in your build pipeline. If that cache is ever down or broken or inaccessible from certain build infrastructure, chances are it will get removed from affected build pipelines and those devs are unlikely to come back.
Having said that, of course, GitHub is promoting caches quite heavily here. This might make it actually worth using for the individual devs.