# Mention of Julia for the re-implementation of PETSC

**URL:** <https://discourse.julialang.org/t/mention-of-julia-for-the-re-implementation-of-petsc/46199>\
**Category:** Offtopic\
**Created:** [September 7, 2020, 1:51pm UTC](https://discourse.julialang.org/t/mention-of-julia-for-the-re-implementation-of-petsc/46199 "2020-09-07T13:51:06Z")\
**Posts on this page:** 1\
**Showing post:** 22

<div class="post-metadata">

**Author:** ![Eben60](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/eben60/32/13475_2.png) [@Eben60](https://discourse.julialang.org/u/Eben60)\
**Post date:** [September 9, 2020, 1:02pm UTC](https://discourse.julialang.org/t/mention-of-julia-for-the-re-implementation-of-petsc/46199/22 "2020-09-09T13:02:27Z")

</div>

> [@RoyiAvital](#):
>
> No one would wrap an existing code base in Julia.  
> Let’s say I have a system which is doing some analysis of signals and now I want a new module to address new model of a signal.

Or see [Data-exchange Julia-LabView](https://discourse.julialang.org/t/data-exchange-julia-labview/46315) for another use case: Experiment control by LabVIEW, and e.g. signal analysis with Julia.

---

_[View the full topic](https://discourse.julialang.org/t/mention-of-julia-for-the-re-implementation-of-petsc/46199)._
