> How do you mean? ... so the refactoring still happens independently.
Not all refactors modify APIs, and even some that do can be programmatically applied. Suppose you've deprecated method Foo(..) and have a replacement Bar(..). With access to all the source, you can change things globally, it's great. One funny programming 'mistake' that creeps into code that's been around a while is dodgy looking ternary operators:
return (foo ? true : false)
return (foo ? false : true)
return foo;
return !foo;
My day to day work is almost exclusively C++. Thousands of other engineers are in the same boat as me. We all benefit from a fabulous tools team.
How do you mean? If I refactor the backend, for example, an iOS dev still needs to come in and refactor the iOS app, so the refactoring still happens independently.
> It facilitates code sharing.
That's handy if many or your projects are in the same language, true. That generally didn't hold for the projects I've worked on.
> It provides easy access to examples of how code should be used.
True, but that's mostly the same as having a GitLab instance (or similar) installed.
> You don't deploy source, you deploy packages.
Sounds like I just have different needs, in my area of development (Python server backends) the source is the package.