3 ms·

I don't know much about elixir but I'm interested. Are there disadvantages to this process?

• eXpl0it3r 5y ago
  I'd assume it's incompatible with LGPL code/libraries (unless it's open source), then again I have no idea how widespread said license is in the Elixir world.
  • dnautics 5y ago
    IIRC LGPL says you have to "convey" the code, not "you must bundle the code with your binary", it could be anything from "email this address to request the code" or "send a SASE to this address and I'll send you a CD-ROM". I believe GPL even lets you charge for the code, I could be wrong about that.
    • ipaddr 5y ago
      You can charge someone for gpl code but you can't expect to get paided if others give away that code.
  • goodpoint 5y ago
    Static linking with LGPL is OK as long as you allow users to relink to other libraries. You can do that by shipping the object files with the binary, or on request, or providing the sources of your application under a closed license, or under any FOSS license.
• goodpoint 5y ago
  Yes: dynamic linking allow receiving OS security updates for any library. With static linking you become responsible for: - tracking down the dependencies used during a build - track where the binary is deployed - follow publishing of vulnerabilities affecting the libraries you used - either backport security fixes, rebuild and deploy the binary or deploy a newer version hoping it does not break anything