634 karma · joined April 24, 2018
It's not the opposing side's fault if your solution is practically infeasible and wasteful.
Just as a simplistic example, user set A wants content `x` and `y`, user set B wants content `y` and `z` - data shows that `y` is popular, but by removing `x` or `z` they make those users very reluctant to continue using the service.
I've seen it multiple times with services I use where only the common set is kept and then people start loathing and leaving the service.
Pretending everyone has that choice not to.
Just recently they started playing the exact same ads but sometimes they have a few syllables messed up. I think I now have first-hand experience in being gaslit, it really makes you doubt your sanity if you heard the "same" ad but "wrong".
Because transistors have a capacitance that one has to drive, higher frequency requires more voltage and more voltage means bigger leakage currents which means more heat and power consumption.
I'm also trying to tell you that your whole base premise is wrong, that even expecting some library to work or to keep working is too much (unless you apply one of the solutions I offered). Calling certain behaviors stupid absolutely has a place in a discussion about when people play with fire and then are surprised they get burnt, I think you deliberately missed my point that if you put yourself in danger you only have yourself to blame and most laws do care about that nuance. In the end the job and obligation of keeping the software you write secure is just as much on the person writing some libraries.
We can argue if x or y are effective defense in courts or not but as I said, that hasn't been tried out in the case of open-source software being broken. I also have to repeat that when you look at malicious software and changes in practice then the law applies retroactively and you have to deal with preemptive defense yourself - going back to my first point(s), you have to change the way you develop software instead of hoping what you randomly execute is good.
Hopefully you now understand what I'm trying to say to you better, English isn't my first language, sorry.
Once again I'm reminded about that sentence someone once said. With random open-source libraries you're dealing with something someone else put out there just because they wanted to, having any kinds of expectations that someone will or won't do something is seriously short-sighted and even pretentious. Do you go around running random .exe-s you find from the internet? Why do you do so with the dependencies for your projects and expect a better end result? You may not like to hear this but it's true.
There's two solutions here, either you start reviewing the libraries you use, every release, or sign a support contract that obliges the maintainer to do something you want.