I'm certainly not trying to downplay the seriousness of these issues. But it seems like a equally (it not more) valid title might be something like "HTTP/1: Continues to rear its ugly head" or something like that.
2,657 karma · joined July 15, 2017
I'm certainly not trying to downplay the seriousness of these issues. But it seems like a equally (it not more) valid title might be something like "HTTP/1: Continues to rear its ugly head" or something like that.
_A_ shop being out of stock doesn't mean that there is a shortage, but when all of them are it is.
> It also seems like you're trying to moralize this when it's just about supply and demand
I don't see how you can ignore the moral aspect - there is a massive difference between being able to afford toilet paper vs being able to hire workers at the rate that a corporation wants.
What you are describing is having stores re-price toilet paper to reflect demand. And that would have fixed the shortage. The problem then isn't that toilet paper isn't available, its that its price becomes completely unethical - rich people and not-rich people both have an equal right to toilet paper and pricing it up to level where the less well compensated have a hard time affording it - even if is available - is ethically problematic. Outside of there being laws against price gouging, stores know that customers will never forgive them for this - if you are working at a minimum wage job and you show up to Target and toilet paper costs $150 you could very well swear to never go there again.
That is massively different than what is going on here. We're talking about huge corporations that have spent years reducing their work force that want to increase their work for now and are upset that they can't get the same prices for labor as before. It's not like labor is going to cost 10x as before - it's an incremental increase. And its not like this is some fundamental right - people of all income levels should have a basic right to keep themselves clean. Corporations don't get to dictate what it wants to pay its workers. A 25% bump in toilet paper costs probably wouldn't have fixed the toilet paper shortage. A 25% bump in pay may very well fix this "labor shortage".
They aren't the same things.
This is simply not accurate. memset_s provides that guarantee. memset does not. It would appear that you have been under the impression that it did. However, it did not.
Imagine that you depend on library A of a particular version which itself depends on library B. With minimal version selection, as long you don't bump you dependency on library A (or some other library that depends on library B), you'll continue to get that same version of library B. But, then library B releases a critical security fix. With minimal version selection, there isn't a great way to pick up that fix. You can _hope_ that library A releases a new version that requires the fix - but that may or may not happen and could take a while. Or, you could add an explicit dependency on the new version of library B - which is unfortunate, since, your main package doesn't depend on library B directly.
Lock files solve this problem. You can depend on whatever version of library A that you need and lock the transitive dependencies. And once library B releases its fix, you can update your lock file without having up bump the version of library A.
Tools like poetry providing the features to automate this workflow.
The problem with this approach is that it doesn't handle transitive dependencies well. Say you depend on version 1.4.6 of a particular library. And then that library depends on version >= 2 of some other library. When you install your package, you know that you'll get version 1.4.6 of the first library but have no idea what version you'll get of the second library. You can of course pin all the transitive dependencies - except that clutters up the setup.py and is a massive pain to keep up to date as you bump individual dependency versions.
Imagine this scenario:
1. User visits a site in normal mode. Browser opens connection A. Browser uses connection A to fetch the site. Browser leaves connection A open.
2. User opens private mode. User visits the same site. Browser opens connection B to fetch the site.
How does it matter that connection A was left open if some other connection was used to fetch the site in private mode? If that's not the case, then its a big deal - but that requires some sort of evidence and not just wild hand waving that it could be the case.