| 30 Aug 2024 |
 emily | ooh, we should start calling it "OBLF" so we have another acronym as confusing and misleading as "IFD". | 03:50:55 |
| emily | I didn't actually get around to starting to write the tool for Rust yet, but FWIW I wouldn't necessarily be opposed to extending it to work with other language package sets if that ends up being a thing that would be convenient | 03:51:42 |
| emily | (though I can understand if Go wants a tool written in Go, etc.) | 03:51:57 |
 @adis:blad.is | In reply to @emilazy:matrix.org
Node.js could use a bit of the same treatment, I've noticed I can't even conceptualize what that would look like for node | 03:53:45 |
| emily | hm | 03:54:08 |
| @adis:blad.is |
The Python ecosystem is much worse about following SemVer
They actually don't follow semver at all: https://peps.python.org/pep-0440/
| 03:54:10 |
| emily | because of nested node_modules? | 03:54:14 |
 Winter | nodejs is... hell | 03:54:28 |
| Winter | have you seen the sheer amount of hacks we have to do? | 03:54:38 |
| @adis:blad.is | Because of how many versions of a dependency that needs to coexist in a tree | 03:54:51 |
| emily | right | 03:55:08 |
| @adis:blad.is | And how they need to be compatible | 03:55:19 |
| emily | you can at least canonicalize all the compatible ones, right? | 03:55:19 |
| emily | but yeah the nice thing about Rust and Go is that they have ecosystems that are well-behaved about versioned dependencies | 03:55:31 |
| emily | so it's probably a lot easier to accomplish for them than anything else | 03:55:37 |
| Winter | yeah i'd say let's make this work well with Rust/Go first | 03:55:42 |
| Winter | which is 1000000x more feasible than npm | 03:55:49 |
| @adis:blad.is | I'm not loving the whole FOD situation we have in nodejs. But I don't see a path to a better alternative. | 03:56:34 |
| Winter | it's not perfect, no | 03:56:54 |
| Winter | but it's much better than we had before | 03:56:59 |
| Winter | ideally dynamic derivations would, y'know, be a thing | 03:57:08 |
| Winter | but we're probably years away from thay | 03:57:15 |
| Winter | * | 03:57:19 |
| emily | (oh no, the Nixpkgs issue has been dragged into an upstream Rust argument about the 1.80 situation) | 03:57:37 |
| @adis:blad.is | Winter: You might have missed that I introduced importNpmLock at some point recently-ish? | 03:57:38 |
| Winter | i saw it | 03:57:45 |
| Winter | but i mean for Nixpkgs stuff :) | 03:57:53 |
| @adis:blad.is | It doesn't replace anything from nixpkgs, it's more for local workflows | 03:58:00 |
| Winter | very good to see that my hooks basically Just Work(ed) with it, though! | 03:58:09 |
| emily | to be slightly more on topic, what's the deal with pnpm? good thing? bad thing? | 03:58:20 |
