2 ms·
> I never understood the concept of "optional" library. Consider a scientific software, let's call it x. x can solve many problems and these problems cross-cut
by bayindirh 6y ago
> I never understood the concept of "optional" library.
Consider a scientific software, let's call it x. x can solve many problems and these problems cross-cut a lot of disciplines.
A researcher, user of x has a need for only subset of these features, and configures & compiles x with the features only he/she needs. This has many advantages from simpler setup to shorter build to easier verification.
When you're compiling software on remote, restricted systems; these optional components makes people's life a lot easier. Also, esp. in scientific community, every library needs something lower level so, trying to compile everything in results in exponential dependency hikes. Optional components solve this very neatly.
- dagw 6y agoAnother similar use case that is quite common is that your tool can use one of several different calculation kernels. For example there is one option that is fast but closed source, one that is open source but slower and one option that only works with Nvidia GPUs. Most people won't have all three options available, but as long as you have one of them the software works fine.