# Statically compiled and statically linked

**URL:** <https://discourse.julialang.org/t/statically-compiled-and-statically-linked/12290>\
**Category:** General Usage\
**Created:** [July 10, 2018, 12:23pm UTC](https://discourse.julialang.org/t/statically-compiled-and-statically-linked/12290 "2018-07-10T12:23:12Z")\
**Posts on this page:** 1\
**Showing post:** 29

<div class="post-metadata">

**Author:** ![Mayank\_Gupta](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/mayank_gupta/32/8327_2.png) [@Mayank\_Gupta](https://discourse.julialang.org/u/Mayank_Gupta)\
**Post date:** [August 31, 2020, 7:20pm UTC](https://discourse.julialang.org/t/statically-compiled-and-statically-linked/12290/29 "2020-08-31T19:20:57Z")

</div>

Aha we are talking about two different uses of the word safer. You are talking about safer from a security point of view. I’m talking about safety from a static environment point of view. In the view I’m taking, the completely static environment of a docker container would be a logical conclusion.

Deploying statically linked binaries in a standardized server/computing environment is an important and regular use case. It reduces dependencies and is comparatively much safer than a dynamically linked system.

I agree package\_compiler.jl is part of the solution for this use case. I wanted to explain to Tamas, why people might care for package\_compiler.jl in the first place.

---

_[View the full topic](https://discourse.julialang.org/t/statically-compiled-and-statically-linked/12290)._