Post #2785547

@ekuber@hachyderm.io I disagree. I care a lot more about portability of binaries than the other tradeoffs. That said, I do not vendor the C/C++ code, it's almost always a git subtree or submodule depending on use case. The reason is that I put a great deal of effort into making sure that the library builds for all desktop and mobile operating systems statically (which is a fun surgical operation for Windows half the time). In the case where it's sensible to allow using the system library, that's an env var opt-in. To put this discussion differently: I think that cargo doesn't cater for this use case particularly well and there's an open design space here that could satisfy both of our views without conflicting with either. :D