For example, this could include the distribution of domains among existing Julia packages, the trend in the growth of Julia package numbers, and possibly additional things such as the distribution of developer amounts for each package, code volume distribution, the distribution of API amounts, the distribution of usage amounts, and so on.
Last Juliacon there was a talk analyzing the packages in the General Registry which you might find interesting:
In the “State of Julia” at the same Juliacon was a brief segment about the package ecosystem as well:
There was a bit of discussion about usage stats recently on this forum as well:
There’s been a couple of posts recently by certain people bemoaning Julia’s lack of popularity/usage/growth. Which I find confusing—where is this impression of lack of usage coming from? It’s certainly not the impression I get at all. From where I’m standing it seems like there’s steady, consistent growth in usage, and that Julia is transitioning from an emerging technology to a fairly mature technology that is widely used, although certainly not the most widely used. So I made a few graphs of v…
You can get package download stats for yourself as well:
After some years of getting the package server architecture in place and working (mostly) reliably, @staticfloat and I finally had some time to work on collecting logs into a data warehouse (we’re using Snowflake ) and designing a set of queries over the logs that we can run and publish regularly. The current public aggregated stats are available with the prefix
https://julialang-logs.s3.amazonaws.com/public_outputs/current/
followed by a rollup name and the suffix .csv.gz indicating that all t…
4 Likes
Thanks! I’ll have a look!
