quazeekotl
Joined 9 years ago
Joined 9 years ago
That is absolutely not in evidence.
Most of them _everyone_ knew about for thousands, or even tens of thousands of years, why didn't this "sunlight" disinfect them?
This is objectively untrue by pretty much any measure.
For instance on plenty of health related metrics the US is significantly worse than most first world countries (such as infant mortality), and some regions are worse than even many third world countries (such as Texas).
https://en.wikipedia.org/wiki/List_of_countries_by_infant_an...
44th on this list
The idea that poor people are significantly better off in the USA is a flat out lie.
We already know that the North Korean government is using cryptocoin tech to evade international sanctions to fund their missile and nuclear programs.
How many North Korean non government officials do you suppose were permitted to attend this conference?
Actions like this absolutely enable this terrible regime to perpetuate itself and its horrific actions, they do little or nothing to aid any ordinary North Koreans.
This comes into play when you copy or access huge files that are going to be read exactly once, they will start pushing out untouched program pages to disk, in exchange for disk cache that is completely 100% useless, even to the tune of hundreds of gigabytes of it.
Programs can reduce the problem with madvise(MADV_DONT_NEED), but that only applies to files you are mmap()ing, and every single program under the sun needs to be patched to issue these calls.
You can adjust vm.swapiness systctl to make X larger, but no matter what, programs will start to get pushed out to disk eventually, and cause unresponsiveness when activated. You can reduce vm.swapiness to 1, but if you do, the system only starts swapping in an absolute critical low ram situation and you encounter anywhere from 5 minutes, to 1+ hour of total, complete unresponsiveness in a low ram situation.
There _NEEDS_ to be a setting where program pages don't get pushed out for disk cache, peroid, unless approaching a low ram situation, but BEFORE it causes long periods of total crushing unresponsiveness.
Completely understandable to move the upstream repo away from Apple, I don't think there's much else to it. He's been very active in the fork AFAICT.
His Sponsors page: https://github.com/sponsors/michaelrsweet
[1] https://github.com/apple/cups/graphs/contributors
[2] https://www.msweet.org/blog/2019-12-20-left-apple.html