I’ve recently deleted a fork of an Objective-C library that was popular 5/6 years ago. The fork added a feature that was eventually implemented in the library (not via my PR).
I’m receiving emails of users whose build I’ve just broken with my move.
Source dependencies risk? 
-
Show this thread
-
This Tweet is unavailable.
-
Gabriele Petronella Retweeted Gabriele Petronella
Yeah, or this other piece or advicehttps://twitter.com/gabro27/status/1004368442311528449?s=21 …
Gabriele Petronella added,
0 replies 0 retweets 1 like -
This Tweet is unavailable.
-
Yeah, I believe source deps have their place in a sane ecosystem. I'm sure sure I buy the availability argument though: it doesn't change much from downloading binary deps. Other arguments (e.g making a quick change to third party deps) are more compelling though
0 replies 0 retweets 0 likes -
This Tweet is unavailable.
-
Ah yeah, I was mostly referring to the original tweet. Depending on source or Ok binary doesn't change much in case the dependency becomes unavailable.
1 reply 0 retweets 0 likes
At least if a binary dependency ceased to exist it would be because the entire binary distribution service had gone away.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.