# Not only for technical computing: changing the narrative around the usecase for Julia

**URL:** <https://discourse.julialang.org/t/not-only-for-technical-computing-changing-the-narrative-around-the-usecase-for-julia/19784>\
**Category:** Community\
**Created:** [January 18, 2019, 1:58pm UTC](https://discourse.julialang.org/t/not-only-for-technical-computing-changing-the-narrative-around-the-usecase-for-julia/19784 "2019-01-18T13:58:30Z")\
**Posts on this page:** 1\
**Showing post:** 28

<div class="post-metadata">

**Author:** ![Liso](https://avatars.discourse-cdn.com/v4/letter/l/898d66/32.png) [@Liso](https://discourse.julialang.org/u/Liso)\
**Post date:** [January 18, 2019, 11:03pm UTC](https://discourse.julialang.org/t/not-only-for-technical-computing-changing-the-narrative-around-the-usecase-for-julia/19784/28 "2019-01-18T23:03:56Z")

</div>

I propose to think about these clever words before doing blog post:

> [@List of working packages on v. 1.0](https://discourse.julialang.org/t/list-of-working-packages-on-v-1-0/13779/52):
>
> Just to adjust expectations: waiting an extra month or six would not have made Julia polished in the sense Matlab/R/Stata/… is. The package ecosystem will probably take years to develop mature libraries. In a lot of ways, 1.0 is the beginning of the journey, not the end; having a stable release should facilitate focusing on packages. Many are already using Julia productively, and have been doing that for years. There is a price to pay in terms of convenience, but there are also great benefits.…

---

_[View the full topic](https://discourse.julialang.org/t/not-only-for-technical-computing-changing-the-narrative-around-the-usecase-for-julia/19784)._