I want to open up a discussion regarding the state of the Eco-System. from over 1000 packages only a subset is actually useful. Some are just plain broken since Julia is still introducing breaking changes. Some are way under documented and thus not so useful, some are too specific to be a package…

Related discussions: [image] Obsolete packages? Internals & Design Looking through pkg.julialang.org I noticed quite a few packages that look to be obsolete (n years since being updated, all tests failing). I had a go at “adopting” one recently, and made a PR, but I suspe…

And also [image] Should a sort of quality-assurance program introduced for Julia packages? Community 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 pre…

Pkg3 will bring namespaces, and we’ll likely have some kind of curated namespace for known-high-quality packages. There are some real issues here around curation and discoverability of packages, but vetoing packages based on subjective worth isn’t the right solution, and it’s a bad route to go down…

[image] MikeInnes: vetoing packages based on subjective worth isn’t the right solution However, some (very permissive) objective criteria could help, like removing packages from certain lists if the package has not passed unit tests for a year or more, or has not achieved some minimum level o…

I totally agree. In addition: There are a number of high quality packages that are both small, self-contained, and abstract in nature. I’ve noticed a few cases where larger packages reimplement functionalities that these small packages already include (or where literally made for). This code dupli…

[image] MikeInnes: Pkg3 will bring namespaces, and we’ll likely have some kind of curated namespace for known-high-quality packages. There are some real issues here around curation and discoverability of packages, but vetoing packages based on subjective worth isn’t the right solution, and it’s…

I would be curious if there are a lot of libraries which are currently are outdated, but where the original authors had planned to restart post 1.0 (when they expect API stability and the general number of users to rapidly increase). Even if not, there may be people willing to take over the older l…

[image] jlperla: On another note, I spent a bunch of time over the last few weeks getting a sense of the ecosystem, and found it very hard to find functionality as opposed to just packages. One way I like to search is through the big orgs. For example, for statistics I just go straight to Jul…

@ChrisRackauckas Thanks! One way I like to search is through the big orgs. For example, for statistics I just go straight to JuliaStats and search there. Of course there’s good stuff not in orgs, but usually (the big) orgs have a testing and maintenance structure that keeps packages alive, while …

[image] jlperla: The problem is that github doesn’t support (or I can’t figure out!) how to search code within an organization rather than searching in the repository itself. If you go to the org main page and search, it’ll search all repos of an org. [image] jlperla: If it is indexing t…

State of the Eco-System

Meta Discussion

Tamas_Papp November 24, 2017, 12:16pm 3

And also

3 Likes

Topic		Replies	Views
How can we create a leaner ecosystem for Julia? Statistics package , proposal , time-series , machine-learning	101	10840	October 15, 2020
Fixing Package Fragmentation Community	71	6294	May 28, 2023
How to know if a package is good? Community	105	7340	June 13, 2022
Post list of all registered packages Community question	19	3434	April 2, 2019
The State of the Julia Ecosystem Community	109	8979	January 31, 2019

State of the Eco-System

Related topics