3 ms·
> the absolute insanity that comes with it's build systems/third party dependency management. Well yes, that would kill me too, if I actually expected the lang
by PaulDavisThe1st 5y ago
> the absolute insanity that comes with it's build systems/third party dependency management.
Well yes, that would kill me too, if I actually expected the language to come with a single blessed dependency that addresses functionality <Foo>, that I will never want or need to patch the blessed dependency, and that there would be only one way to actually build a program or library.
But it doesn't kill me because I don't expect either of those things.
The dependency stack for my (21 year old) project consists of 86 3rd party libraries that on an x86_64 platform take up about 2GB after compilation. This is intimidating and sometimes painful, but I don't find it insane in any way. We have patches for a half-dozen of the deps that will never make it upstream and we have to be sure that we compile the libraries in the precise way that we need them (for example, we require the thread-safe version of libfftw, not the regular version).