Post #2340697
2026-05-06 13:52 UTC
@arclight@oldbytes.space Prior to the current LPM regime, library code that wasn't yet vetted and deemed important enough to be included in distros was only really visible to people with adjacent domain expertise to evaluate whether they wanted to use it by copying it into their project or having users obtain it manually out-of-band.
This produced a sort of organic process and feedback loop by which it could be established if anyone had the will to be responsible for large-scale use of the code.
Replies (1)
-
@jannem@fosstodon.org 2026-05-06 14:11
@dalias@hachyderm.io @arclight@oldbytes.space I think that's an important and useful distinction. There's a fundamental difference between "You search, find and download a library to use with your code"; and "You follow an intro tutorial and the tool chain pulls it down as a secondary dependency without you even knowing what it is, or that it was going to happen."