Post #2563354
2024-08-27 16:23 UTC
@nobody@mastodon.acm.org @stargirl@hachyderm.io I'll note that this suffers from Zooko's triangle, a trilemma in nominal logic: https://en.wikipedia.org/wiki/Zooko%27s_triangle
Imagine every Python module were content-addressed somehow, and packages too. This only kicks the can down the road, because you'd probably rather import from a petname than from a SHA-256 hash, so somebody must now set up a petname-to-hash map, and all of the existing political issues of the Cheeseshop reappear upon the maintenance of that map. (This is why politics is an inevitable part of maintaining large ports trees too.)
Replies (2)
-
@nobody@mastodon.acm.org 2024-08-27 16:25
@corbin@defcon.social @stargirl@hachyderm.io Um to be clear, the intention would not be to make developers write `import from package_name_${hash}`, but to generate hints for the import system at build/install time
-
@moonchild@social.applied-langua.ge 2024-08-28 03:01
@corbin@defcon.social @nobody@mastodon.acm.org @stargirl@hachyderm.io petname as display only solves this problem (among others)