# State of DSP?

**URL:** <https://discourse.julialang.org/t/state-of-dsp/1559>\
**Category:** Signal and Image Processing\
**Tags:** dsp\
**Created:** [January 18, 2017, 5:24am UTC](https://discourse.julialang.org/t/state-of-dsp/1559 "2017-01-18T05:24:47Z")\
**Posts on this page:** 1\
**Showing post:** 11

<div class="post-metadata">

**Author:** ![TsurHerman](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tsurherman/32/1234_2.png) [@TsurHerman](https://discourse.julialang.org/u/TsurHerman)\
**Post date:** [July 30, 2017, 8:41pm UTC](https://discourse.julialang.org/t/state-of-dsp/1559/11 "2017-07-30T20:41:24Z")

</div>

The best thing would be if we could have a “Julia code exchange” a place to share codes and algorithms even if they are partial and do not cover the whole range of possibilities.

If you wrote something for array of Float32 which is useful for me but I need it to support other types , it’s fairly easy.  
Or someone might get inspired to take an algo and cater for all the corner cases and publish it as part of Package.

We can benefit greatly if we share code and algorithms that do not yet warrant a new package or are in state clean enough to publish as a package.

In works great in Matlab file exchange.

Preferably each shared code will be in file or will have a single file to include, and some documentation on what and how.

By the way , algorithms written to support only single float are way easier to understand and modify than algorithms that have extra spaghetti of overloads to cater for all cases.  
Actually algorithms are better shared that way …

---

_[View the full topic](https://discourse.julialang.org/t/state-of-dsp/1559)._