mastodonien.de

fosstodon.org

Zeitpunkt              Nutzer    Delta   Tröts        TNR     Titel                     Version  maxTL
Mo 08.07.2024 00:00:19    61.922      +5    3.524.369    56,9 Fosstodon                 4.2.10     500
So 07.07.2024 00:00:04    61.917       0    3.522.885    56,9 Fosstodon                 4.2.10     500
Sa 06.07.2024 00:00:07    61.917      -2    3.523.632    56,9 Fosstodon                 4.2.10     500
Fr 05.07.2024 00:00:27    61.919       0    3.520.710    56,9 Fosstodon                 4.2.10     500
Do 04.07.2024 00:00:52    61.919      +2    3.517.337    56,8 Fosstodon                 4.2.9      500
Mi 03.07.2024 00:00:12    61.917      +2    3.513.906    56,8 Fosstodon                 4.2.9      500
Di 02.07.2024 00:01:44    61.915      -2    3.510.479    56,7 Fosstodon                 4.2.9      500
Mo 01.07.2024 00:00:33    61.917       0    3.507.420    56,6 Fosstodon                 4.2.9      500
So 30.06.2024 00:00:34    61.917      +2    3.504.671    56,6 Fosstodon                 4.2.9      500
Sa 29.06.2024 00:01:13    61.915       0    3.501.982    56,6 Fosstodon                 4.2.9      500

Mo 08.07.2024 12:52

We sometimes confuse packages providing a command-line interface as "applications". Sometimes, developers justify not making their package programmatically usable, by calling it a tool, application or CLI-only package.

But in my opinion, all packages are libraries. Within a given ecosystem, if someone can depend on your project, then your project is a library, because it can and will be used as such.

WDYT?

GitHub comment screenshot, saying: In my experience though, as someone who glues a lot of Python

GitHub comment screenshot, saying: In my experience though, as someone who glues a lot of Python "tools" together, many projects that consider themselves applications (or CLI tools, or any other name that doesn't imply "library") are actually libraries. In my experience again, all Python packages are libraries. I'll go further: all packages are libraries, whatever the ecosystem. If you're in the ecosystem, you (willingly or not) play by its (resolution) rules, and you should be a kind fellow citizen. If you can depend on an "application", whether you consume it or not, then you can use it as a library. We should never underestimate the imaginative ways developers can consume or depend on something 😉 True applications are projects which are not packaged within this ecosystem. They are above it. True applications simply provide an install script, a requirements.txt file, a ZIP file, or whatever suits the devs of the application and their users, but they do not exist within the underlying ecosystem(s) (ecosystems can be layered).

[Öffentlich] Antw.: 0 Wtrl.: 1 Fav.: 0

Antw. · Weiterl. · Fav. · Lesez. · Pin · Stumm · Löschen