# Static Arrays in pure Julia

**URL:** <https://discourse.julialang.org/t/static-arrays-in-pure-julia/46030>\
**Category:** Performance\
**Tags:** package, performance, array\
**Created:** [September 3, 2020, 10:52pm UTC](https://discourse.julialang.org/t/static-arrays-in-pure-julia/46030 "2020-09-03T22:52:55Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![stevengj](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/stevengj/32/71_2.png) [@stevengj](https://discourse.julialang.org/u/stevengj)\
**Post date:** [September 3, 2020, 11:01pm UTC](https://discourse.julialang.org/t/static-arrays-in-pure-julia/46030/2 "2020-09-03T23:01:51Z")

</div>

> [@Renan\_Rabelo](#):
>
> I found a package called “StaticArrays” and it says that StaticArrays can perform up to 25x faster than dynamic, so why does Julia don’t use this as a core feature?

First, the [StaticArrays package](https://github.com/JuliaArrays/StaticArrays.jl) is _already pure Julia code_.

Second, StaticArrays aren’t a panacea — as [I pointed out recently in another thread](https://discourse.julialang.org/t/julia-hangs-while-displaying-an-smatrix/45918/3), they are only good for problems involving lots of tiny arrays whose size is fixed at compile-time, and aren’t a good idea as a general-purpose container.

Third, one of the key design goals of Julia is that code does not have to be “built-in” to the core language to be fast — for the most part, the standard library has **no advantage over external packages** except being installed automatically. In particular, there is no performance advantage to being “built in”.

---

_[View the full topic](https://discourse.julialang.org/t/static-arrays-in-pure-julia/46030)._