# State of the Eco-System

**URL:** <https://discourse.julialang.org/t/state-of-the-eco-system/7285>\
**Category:** Meta Discussion\
**Created:** [November 24, 2017, 11:43am UTC](https://discourse.julialang.org/t/state-of-the-eco-system/7285 "2017-11-24T11:43:49Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Tamas\_Papp](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/tamas_papp/32/25949_2.png) [@Tamas\_Papp](https://discourse.julialang.org/u/Tamas_Papp)\
**Post date:** [November 24, 2017, 12:16pm UTC](https://discourse.julialang.org/t/state-of-the-eco-system/7285/3 "2017-11-24T12:16:35Z")

</div>

And also

> [@Should a sort of quality-assurance program introduced for Julia packages?](https://discourse.julialang.org/t/should-a-sort-of-quality-assurance-program-introduced-for-julia-packages/6346):
>
> Just a thought. The inclusion of a package in METADATA is currently conditional only to formal considerations… if the tag is in the right format, if the require file is present and so on… but no “judgment” on the quality of the code nor on the relevance of the package is made. While I appreciate this “open” approach, I also appreciate those when some sort of QA is employed. In particular I liked the experience I had to develop [Drupal](https://www.drupal.org) modules (Drupal is a web Content Management System). In that…

> [@Pruning and quality control for the package ecosystem](https://discourse.julialang.org/t/pruning-and-quality-control-for-the-package-ecosystem/7021):
>
> Related to [previous discussion](https://discourse.julialang.org/t/ann-higherprecision/6956) on starting new projects in place of abandonned ones (also see [this one about QA](https://discourse.julialang.org/t/should-a-sort-of-quality-assurance-program-introduced-for-julia-packages/6346/3)), I found [this short blog post](http://esr.ibiblio.org/?p=7303) where Eric Raymond discusses similar issues about Rust interesting. Some quotes: when the question is “where do I get feature X?” the answer “oh, there are 23 crates for that” is objectively terrifying […] As a potential Rust user, what I want to do is be able to go from a given feature requirement to one high-quality implementation with an implicit …

---

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