# Matlab figure replacement

**URL:** <https://discourse.julialang.org/t/matlab-figure-replacement/74942>\
**Category:** Visualization\
**Tags:** io\
**Created:** [January 20, 2022, 2:57pm UTC](https://discourse.julialang.org/t/matlab-figure-replacement/74942 "2022-01-20T14:57:32Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![fph](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/fph/32/17159_2.png) [@fph](https://discourse.julialang.org/u/fph)\
**Post date:** [January 21, 2022, 2:34pm UTC](https://discourse.julialang.org/t/matlab-figure-replacement/74942/12 "2022-01-21T14:34:16Z")

</div>

> [@ohmsweetohm1](#):
>
> By risky I mean that it could happen that the serialized version is pure garbage and can not be re-opend.

I don’t have much experience, but [here](https://discourse.julialang.org/t/what-is-the-preferred-way-to-save-variables/21918/38) @[kristoffer.carlsson](https://discourse.julialang.org/u/kristoffer.carlsson) claims that

> In my opinion, Serialization has proven to be significantly more stable between Julia versions than many other packages that claim to be so.

YMMV.

Also, note that you can make your code shorter/simpler with `serialize("figure.makie", f1)` and `f2 = deserialize("figure.makie")`.

---

_[View the full topic](https://discourse.julialang.org/t/matlab-figure-replacement/74942)._
