modern programming is like,
"if you're using bongo.rs to parse http headers, you will need to also install bepis to get buffered read support. but please note that bepis switched to using sasquatch for parallel tokenization as of version 0.0.67, so you will need the bongo-sasquatch extension crate as well."
old-time programming is like,
"i made a typo in this function in 1993. theo de raadt got so angry he punched a wall when he saw it. for ABI compatibility reasons, we shan't fix the typo."
@liw @saddestrobots exceot you don't get to choose the level of stability that suits you. Others choose it for you. And you choose it for everyone else.
@wolf480pl @saddestrobots Hmmm. I choose my dependencies, and part of that is evaluating their stability. I don't allow others to impose work on me, such as by requiring the stability I provide, unless they compensate me, or I feel like it.
@liw @saddestrobots where do you find those stable dependencies? IIRC even gcc isn't fully backwards-compatible these days
@wolf480pl @saddestrobots I think you are trying to make a point, but I am entirely failing to understand what it is. However, I'm not interested in combat by debate, so I'll bow out of this discussion now.
@liw @saddestrobots
Sorry, that was a bit too combative on my part.
What I meant is that I find it difficult and frustrating to try to find dependencies that have similar stability guarantees to the kernel.
What's even more frustrating is that often the programming languages in which those dependencies are written aren't themselves stable.
Which is why I feel like I don't have much choice in deciding how much change comes my way from upstream.