| ▲ | cookiengineer 11 hours ago | |||||||
Fun fact: You still can't build the vllm container with updated dependencies since llmlite got pwned. Either due to regression bugs, or due to impossible transient dependencies in the dependency tree that are not resolvable. There is just too much slopcode down the line, and too many dependencies relying on pinned outdated (and unpublished) dependencies. I switched to llama.cpp because of that. To me it feels more and more that the slopcode world is the opposite philosophy of reproducible builds. It's like the anti methodology of how to work in that regard. Before, everyone was publishing breaking changes in subminor packages because nobody adhered to any API versioning system standards. Now it's every commit that can break things. That is not an improvement. | ||||||||
| ▲ | 2ndorderthought 10 hours ago | parent | next [-] | |||||||
Write only code is such a bad bad idea. No one is reviewing 20k loc PRS with 15 new dependencies in an afternoon. Sorry it's just not happening I don't care how many years you have been a software engineer. Yet that's the new thing and how we all are supposed to work or else we are all Luddites. | ||||||||
| ||||||||
| ▲ | cybercatgurrl 9 hours ago | parent | prev [-] | |||||||
slopcode is a pejorative that means nothing to me. if you have an actual criticism to make, then do it | ||||||||