Recent searches
Search options
React builds were failing in India only because the government blocked a website so it would make gradle fail to build. I often think about this, frameworks can be nice but as they have freedom to pull other packages when needed it can break for any sort of unrelated reasons
https://github.com/facebook/react-native/issues/49115#issuecomment-2634609323
@djlink my server and/or domain names are for some reason blocked in Saudi Arabia.. I guess they found out I’m trans 
@codecat uff wtf- how did you found? user report?
@djlink yeah several people from there came to ask for support - all I can do is recommend a VPN lol
@djlink The whole package manager approach is so volatile. Not only are there connection risks, but also random breaking changes and even the possibility of stuff disappearing or an update introducing malware.
I’ve seen big projects set up their own package sources/cache servers just to have a bit more control over the madness. Any experienced developer will also use exact version numbers for the references to prevent bad surprises.
Sometimes Chef runs will fail because if a cookbook depends on a ruby gem it always checks rubygems.org even if it's already installed. So if the site goes down or is overloaded ... it's so dumb.
So then you gotta setup a local caching rubygems proxy and try to use that.
They did finally add a setting to not do this but last I checked it wasn't in a release yet.
How has this been default behavior for over a decade? How can you even quantify the amount of wasted bandwidth and electricity?