Taken from a Slack discussion: I’ve had colleagues comment that fragmentation is currently the only really bad thing of the Julia ecosystem. They miss the numpy/scipy monolithic approach. Now for most package ecosystems the bus factor probably follows some kind of power law, but the vibe I get …

This kind of feels like two separate issues: Big packages that are broken up into several small ones with perhaps a top level package re-exporting those methods. Most of the time a single or small team of contributors are maintaining all of these packages. Many packages that are trying to achi…

[image] ParadaCarleton: a pretty flippant response My response was flippant, because I consider the proposal (especially the part about forcing merges, or making it more difficult to create new packages) absurd. But I should have explained that in detail, instead of resorting to sarcasm. I w…

[image] Tamas_Papp: If some users are willing to maintain a registry of curated packages, they can do so today, without any hassle. That’s really a GREAT idea!

[image] mohamed82008: I understand that but an author can also just add more contributors to the project with merge rights. Worst case scenario, an org can fork a project (or copy-paste it and give credit) if a project is abandoned but is still important to an org. So there is more than one solu…

[image] ChrisRackauckas: But that relies on luck There is 0% luck involved in forking a project, it always works :sweat_smile: Of course, I see the value in being affiliated with a well funded org but I am just saying that no one should feel pressured to join an org. A GitHub org is just a gr…

[image] Tamas_Papp: Consolidation does happen in the Julia ecosystem, but it is a slow process, and usually involves a lot of work. Simply appointing a “czar” is not going to make this magically happen any faster. When you have packages that are functioning OK and each has a set of users, consol…

We’ve had this discussion (more focused on statistics) already: [image] How can we create a leaner ecosystem for Julia? Statistics Comparisons of Julia w/ other languages often say one disadvantage of Julia is that it has fewer 3rd party packages. I tend to disagree. Jul…

Most of this has been touched on before but that doesn’t mean it’s not worth revisiting with renewed energy and direction; but I’m not sure how helpful it is to try to address all of these problems that require different solutions in a single thread. If it make anyone feel any better, this did kic…

[image] Tamas_Papp: If some users are willing to maintain a registry of curated packages, they can do so today, Unfortunately, it’s a bit backward. Most of the packages that we’d like in our curated registry are already in the general registry. What would be more useful would be a copy of Gen…

Whats the benefit of maintaining a personal registry for packages that are already in the general registry

What are the externalities of registering packages in the general registry? Should I feel bad about the dozens of packages I already registered?

Fixing Package Fragmentation

Community

nilshg May 13, 2023, 3:20pm 45

We’ve had this discussion (more focused on statistics) already:

Topic		Replies	Views
How can we create a leaner ecosystem for Julia? Statistics package , proposal , time-series , machine-learning	101	10941	October 15, 2020
Discussion on "Why I no longer recommend Julia" by Yuri Vishnevsky Community discussion	298	50328	September 9, 2022
The present and the future of package registration Package Management	80	2621	June 11, 2023
How to know if a package is good? Community	105	7474	June 13, 2022
Reduce package registration waiting period Meta Discussion	83	4379	June 10, 2020

Fixing Package Fragmentation

Related topics