Timeline for Build systems/development environments allowing alternate/backup dependencies
Current License: CC BY-SA 4.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 15, 2021 at 19:26 | comment | added | Becuzz | It certainly can pay off. It's just something that, in my experience, is something to do carefully. I've seen times where it has paid off. But I've seen plenty of times where it hasn't or has been done so poorly that it can't ever be reused. I'm all for doing it where it makes sense. Figuring out where it makes sense is the difficult part. | |
| Dec 15, 2021 at 18:42 | comment | added | davidbak | Yes, it's up-front work to create the insulating interfaces but it pays off. The cost (and tediousness) of doing it, however, means it most often isn't done, and that's when you get problems like this where you can't swap out dependencies. Mostly because #1) lots of scattered code changes and #2) use of convenient features provided by the dependency that are more than you really need, but you used them because they were convenient, and it turns out other packages that could do what you mostly need don't have these extra features ... | |
| Dec 15, 2021 at 17:46 | history | answered | Becuzz | CC BY-SA 4.0 |