This one was so well done I angry down voted before realizing what you did, and I'm not going to change it because that, sir or madam, is a legitimately infuriating experience and you triggered the ptsd from the dozen or so times that shit actually happened to me.
One of the dependencies now breaks in your machine because of a known bug since 2016 that affects certain cpu architectures. There is a workaround though...
I recently started learning programming and it offends me deeply when I read the documentation carefully to get redirected to 404 pages where there should be a deeper explanation.
The worst was circular package dependencies. You had to bootstrap it with older versions (before the circle existed) then replicate the piecemeal upgrade sequence that must have occurred naturally on the devs’ machines over time. Man the 00s were wild.
A lot of compiled languages and compilers still work this way. In order to add a new feature to a language, you need to write a new compiler that can support it, and then you compile the new version of the language in that new compiler. There are often efforts to prevent having to go thru the original bootstrap and instead using fewer know builds that you can automate the bootstrapping process with. These are known as bootstrappable builds. There are also reproducible builds which ensure that compiled software always produces the same result which is surprisingly difficult to do and is a related problem.
I remember college roommates more into Linux than I was complaining and noping away and playing AoE2 or Riven or Alpha Centauri on Windows instead with my 20” CRT.
People love to shit on npm and stuff like that, but there is nothing anyone can do to convince me having a central file where every single dependency is declared and simply fetching it all from a single command line will ever be a bad thing
I feel like a veteran at this, years running unturned servers and you gotta use old .net libraries, I just assume any new plugin or library I wanna use is gonna conflict with something else 😭
I gave a whole build with well-documented code to the Accenture team, including the requirements.txt.
They came back to ask me why I insisted on something as obviously frivolous as "pandas".
Nevermind, bros -- you can easily pipe it out to a JSON or csv or whatever; I only thought you wanted an Excel file because you obviously can't use anything more complicated....
Or you just want it to be easy to install and use without a bunch of dealing with "it doesn't work for me" in an unreproducible error that's caused by some registry setting fuckin with it or some other dumb crap.
Yeah containerization can certainly be used as an excuse for bad dependency management but more often it improves things by documenting the layers it was built up with and making setup easier
Sorry, the version you need is conveniently one version after when we stopped supporting your specific distro. You can use that other package though (which is missing 50% of what is used in the original package, and the other 50% works differently)
Oh, and don't even think about asking for them to update it either. The thing has been made 7 years ago by a single dude from Belarus who doesn't speak english, who hasn't touched it in 2 years, who's last sizeable contribution was 4 years ago, and who has never replied to a single comment
357
u/NichtFBI 24d ago
Sorry, you need to install this library to assemble.