# Blog post: Rust vs Julia in scientific computing

**URL:** <https://discourse.julialang.org/t/blog-post-rust-vs-julia-in-scientific-computing/101711>\
**Category:** Offtopic\
**Tags:** rust\
**Created:** [July 17, 2023, 10:17pm UTC](https://discourse.julialang.org/t/blog-post-rust-vs-julia-in-scientific-computing/101711 "2023-07-17T22:17:20Z")\
**Posts on this page:** 1\
**Showing post:** 87

<div class="post-metadata">

**Author:** ![jakobnissen](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jakobnissen/32/13477_2.png) [@jakobnissen](https://discourse.julialang.org/u/jakobnissen)\
**Post date:** [July 20, 2023, 7:59am UTC](https://discourse.julialang.org/t/blog-post-rust-vs-julia-in-scientific-computing/101711/87 "2023-07-20T07:59:18Z")

</div>

> Can you show some example(s) of those type instabilities in cases where they are actually relevant (not by design)?

I think type instabilities that are by design are still problematic. For one, they prevent static analysis of your program. Both by blocking inference and by spamming the JET output so you miss the real issues Eventually, they might also prevent compilation of your program to static binaries (but let’s see).

Some examples of this are:

- Spurious instabilities in Base. These tends to be quickly fixed. Examples include #49801 and #48420
- Instabilities intentionally added to curb compile times. These are typically in print- and show-related methods
- Instabilities in packages, due to design issues. This is rampant in Pkg, in Artifacts and in some packages like FilePathsBase.

---

_[View the full topic](https://discourse.julialang.org/t/blog-post-rust-vs-julia-in-scientific-computing/101711)._