This phenomenon of bad software isn’t new. Vernor Vinge mentioned this in passing in A Deepness In The Sky.
I do agree with the nature of self sufficiency. That is the start of durability. Most people find this revolting though. The goal, for most people, isn’t stuff that works properly. The goal is inclusion and comfort, a social baseline opposed to a utility baseline.
I hoped it would most of all meant not using LLMs, but this is good as well
At some point we might be able to be confident that the current version of all our dependecies has been carefully reviewed by enough reliable people, but right now we're not even moving in that direction; so, minimizing the dependencies is the proper thing to do.
Until customer Barry chimes in that he wants "this" feature, which they are never going to use, but they are also customer who is making 30% of your whole revenue. You can either say no and give opening to your competitor while keeping your ideals, or do what they want.
Have seen too many cases where 10-20 lines of code avoided the need to pull in an external library with multiple dependencies.
Ironically, I also find for anything not extremely mainstream, external libraries tend to appear more complete/functional than they actually are. Often find I end up having to fork and/or rewrite them for my use case.
Sure, some say everything should be fixed with PRs. But my technical goals and timeline constrains don’t necessarily align with the maintainer’s. So fork/rewrite it is!!
10 comments
[ 3.0 ms ] story [ 36.6 ms ] threadI do agree with the nature of self sufficiency. That is the start of durability. Most people find this revolting though. The goal, for most people, isn’t stuff that works properly. The goal is inclusion and comfort, a social baseline opposed to a utility baseline.
At some point we might be able to be confident that the current version of all our dependecies has been carefully reviewed by enough reliable people, but right now we're not even moving in that direction; so, minimizing the dependencies is the proper thing to do.
Utterly bizarre rant.
Have seen too many cases where 10-20 lines of code avoided the need to pull in an external library with multiple dependencies.
Ironically, I also find for anything not extremely mainstream, external libraries tend to appear more complete/functional than they actually are. Often find I end up having to fork and/or rewrite them for my use case.
Sure, some say everything should be fixed with PRs. But my technical goals and timeline constrains don’t necessarily align with the maintainer’s. So fork/rewrite it is!!