3 ms·
It really sucks to manage shared libraries, across many clients in a few languages. Any update requires updating the version everywhere, and you have to indepen
by sanderjd 4y ago
It really sucks to manage shared libraries, across many clients in a few languages. Any update requires updating the version everywhere, and you have to independently debug which version of which library was being used by which application at the time a bug occurred. It works, it isn't impossible, obviously lots of people manage it successfully (polyrepos are more common than monorepos in my experience), but it's a giant pain and it sucks.
- lmm 4y ago> Any update requires updating the version everywhere Much of the benefit of using an IDL like this is to be (mostly) forward compatible, so you don't have to upgrade everywhere immediately. > you have to independently debug which version of which library was being used by which application at the time a bug occurred You have to do that anyway; it's easier if your repository history reflects the reality of which applications were upgraded and deployed at which times. There's nothing worse than having to debug a deployed system that was deployed from parts of a single repo but at several different points in that repo's history.