A modern programming language that makes developers happier.

kotlinlang

We've passed another thousand kotlin libs at 9007 kotlin libraries on MavenCentral after last night's <http://kamp.petuska.dev|kamp.petuska.dev> scan! An increase of 977 since 2022-03-17.
Apologies for the spam - over and out! :kotlin-intensifies: :kotlin-intensifies-purple:

Good dynamics. Do you have a plot somewhere?

No, but if you search for "kamp" in <#C0BJ0GTE2|feed> you should surface enough data points to plot it yourself

I used to post such numbers every 500libs and now padded that to every 1000libs

Kamp 2.0 will have a statistics page to let you plot the data by time, targets, etc... But I have no ETA when that will be ready

I know. But it seems like dynamics looks too good, for not showing it.

Totally agree, but I've been spread too thin recently to be able to focus on that :grinning:

We have 136k KMP artefacts in the Package Search index :slightly_smiling_face: <https://package-search.jetbrains.com/>

FYI some stats are currently broken, we're aware of that

Key word here is artefacts. Kamp groups them all up under a single logical "library" unit. I.e. if a lib publishes artefacts for 10 targets, it would still count as a single mpp lib

However your 136k is still way too big to be explained by just the target artefacts. How do you define an MPP lib in that count?

Also is your artefact a single published file (pom, jar, etc...) Or a maven module?

Looks like the results for `io.coil-kt` are out of date? It says the latest release is `2.0.0-alpha09`

Yes, it's a known issue with the scanner. Basically if there's a package at the group level, it picks it up and does not scan deeper. <https://github.com/mpetuska/kamp/issues/61>

So a good number of kmp libs might still be hidden because of that.

<@UL1A5BA2X> yes agreed that "artefacts" is a vague definition. I think, but need to check, that it's the number of KMP versions of all KMP libs we have in the index. Some numbers are a bit dodgy in our stats as I mentioned earlier; this could be likely if it's the number of artefacts of KMP versions of KMP libs, which is a fairly useless metric :joy:

Unfortunately I'm in the US so comms with the person who worked on that, who's in Taiwan, will be difficult for a couple weeks

Thanks, I'd really like to know more about your metrics since your numbers are vastly different, even though both approaches seem to be similar :smile: I also noticed that for example kotlinx-coroutines-core and kotlinx-coroutines-core-js are both listed on the package search, implying that they're counted individually.

I have to admit I'm not overly familiar with the logic here :) I'll try to find out

Looking at the code, seems like it's indeed counting each version of each artifact of each group where it detects it's KMP (based on Gradle Metadata, right now)