TrentonZero on Nostr: I suspect it is because dependency systems always add transitive dependencies to a ...
I suspect it is because dependency systems always add transitive dependencies to a namespacing system that isn't designed to support them.
So the instant A depends on B that depends on C1.0.0, and A depends on D that depends on C2.0.0, now A has to either depend on C1.0.0 or C2.0.0. Either way could break something.
Unless the underlying system allows for isolating the two namespaces. (I'm not aware of any that do, but doesn't mean they don't exist.) If any did allow for that isolation, it would make it harder to use (up-front) and easier to use (in the long run.) Lots of things seem to fit that pattern. :thinking-emoji:🤔
🤔
>From: (slaninas) at 08/13/22 14:44:45 on wss://nostr-pub.wellorder.net
>---------------
>I wonder why are all the dependency systems broken or annoying to use? Only easy to use and working example I know of is cargo in Rust. But it also has it's downside. Since it's so easy to add dependency, everything has million dependencies.
Published at
2022-08-13 19:51:56Event JSON
{
"id": "592a9bb43eb5f404d8297424c147084ab66cc16dadab8286c3c9040fb9d65be4",
"pubkey": "8098608c9bb2186c7e70f0ed5c0a02f14547a6c1ccd89e411806bc15fd98581d",
"created_at": 1660420316,
"kind": 1,
"tags": [
[
"e",
"6b6e34902348a6511e840f7dbf7826476796050c4136688eb7c29aec021c92c7",
"",
"root"
],
[
"e",
"24d81e21725d075fef5c29f24301e364fa683d4e4fc4b3f14b5333a2995b1dc3",
"",
"reply"
],
[
"p",
"47bae3a008414e24b4d91c8c170f7fce777dedc6780a462d010761dca6482327"
],
[
"p",
"f43c1f9bff677b8f27b602725ea0ad51af221344f69a6b352a74991a4479bac3"
],
[
"p",
"227e0bcb11003c0b10c7e3b2da06f73f3068573df9bac369fe7d859894be1a13"
],
[
"p",
"32e1827635450ebb3c5a7d12c1f8e7b2b514439ac10a67eef3d9fd9c5c68e245"
],
[
"client",
"more-speech - 202208050837"
]
],
"content": "I suspect it is because dependency systems always add transitive dependencies to a namespacing system that isn't designed to support them.\n\nSo the instant A depends on B that depends on C1.0.0, and A depends on D that depends on C2.0.0, now A has to either depend on C1.0.0 or C2.0.0. Either way could break something. \n\nUnless the underlying system allows for isolating the two namespaces. (I'm not aware of any that do, but doesn't mean they don't exist.) If any did allow for that isolation, it would make it harder to use (up-front) and easier to use (in the long run.) Lots of things seem to fit that pattern. :thinking-emoji:🤔\n\n🤔\n\n\u003eFrom: (slaninas) at 08/13/22 14:44:45 on wss://nostr-pub.wellorder.net\n\u003e---------------\n\u003eI wonder why are all the dependency systems broken or annoying to use? Only easy to use and working example I know of is cargo in Rust. But it also has it's downside. Since it's so easy to add dependency, everything has million dependencies.",
"sig": "7e9a6d7f9ae375ec9cb6f4a23005f0a3106d94de1c5a751c18e1e90fd20f287bfc882fa9904a8ce89cb7184995dee236483367947ea1d4d6d8113d5f8a395d2d"
}