This is crucial for security. Otherwise backporting security fixes and/or rebuilding would become impossible.
2,044 karma · joined July 17, 2016
This is crucial for security. Otherwise backporting security fixes and/or rebuilding would become impossible.
You are conflating voluntary donations (which actually happens) with dodging the taxes that everybody is supposed to pay.
Tax avoidance follows the law by the letter but obviously violates the spirit.
If the poor get richer and housing gets more expensive slightly faster, the poor will be homeless in 30 years.
Also job and food insecurity.
https://apps.urban.org/features/wealth-inequality-charts/
https://www.epi.org/publication/top-charts-of-2018-twelve-ch...
If you really need a "container", debootstrap + systemd-nspawn does the job and provides much better sandboxing with 10x less complexity.
You don't need Docker or Nix.
This is the problem: in US the first priority for medical care is profit.
All other aspects are not the first priority, including ethics and psychological health of the patient and the family.
Combine it with a litigation-happy society, greedy insurance companies, and a culture that treats longevity as an entitlement.
Then add the poor focus on prevention and the egregiously lax standards for food/air/water/housing health and safety.
"just"? That's very expensive.
No. If you modify an AGPL network service you have to share the changes. If you call the API from a client you have no obligations.
Don't single out homeless people: one can have bad dental hygiene without being homeless.
(speaking about toxic language...)
Unless you are running unnecessary daemons exposed on the Internet, 99% of the attack surface is from your application and the kernel itself.
Both parts that you can't remove.
Talk about market failures! It's completely obvious that this economical system is not placing the good of the whole human species as its first priority.
Look at the examples on sourcehut.
Yes, it takes a moment to get used to something different, but that's a human problem.
The idea that GPL is ideological and other licenses aren't is false.
Allowing companies to proprietarize software and not caring about user's freedom is just a different set of values.
Those who control the money flow have huge power. Charity was always about giving money while keeping power.
In the last 20 years the growing class of super-billionaires started acting like in a feudal society.
No, you have to understand what is really part of the attack surface and what the attacker wants.
For example, on a properly built system with a single application running with its own user the attacker might have no practical benefit at all in doing a privilege escalation to root.
> running on a physical host with thousands of sleeping VMs
This is a strawman. A shared hypervisor opens another attack surface and was not part of the discussion.
This is hardly reducing the attack surface compared to a good distro with the usual userspace.
It's been decades since attackers relied on a shell, or unix tools in general, or on being to write to disk and so on: it's risky and ineffective.
Many attack tools run arbitrary code inside the same process that has been breached and extract data from its memory.
They don't try to snoop around or write to disk and so on. Rather, move to another host.
The only good mitigation is to split your own application in multiple processes based on the type of risk and sandbox each of them accordingly.
Unfortunately, money brings in risks around project quality and integrity.
Together with reshared count, it implemented a very effective peer review mechanism.
Having high adoption, it provided me very good feeds - nothing comes close now.
A good kernel engineer is paid well above $60K a year.
Just like in academia and industry, our work should be reviewed by peers with relevant and proven experience.
The fact that some thing of NPM installs, github stars and reddit upvotes as a measure of merit says a lot about the immaturity of the software industry.
That's some cheeky phrasing.
> FLOSS is permanently under attack, from the industry
Sure it is, and having a spokeperson that act very poorly in public does not help a bit.
> from the legal framework
Huh?
> NOT going with the flow is exactly what us other people expect RMS to do.
What is "the flow"? Doing very weird things in public? Hitting hard on women at conferences? Pleasing corporations?
> why not do the OpenSource-thing and fork the organisation?
We did: Conservancy, EFF, FSFE are thriving. (Why are you assuming we didn't?)
Second, organizations like Conservancy, EFF, FSFE, and many others don't seem to have any difficulty finding good public speakers.
The idea that we have to choose between RMS and some corporate drone is a false dichotomy plain an simple.
> They want the ability to make modifications, and they want the freedom and transparency that open-source...
Look at all the answers about caring about the user's freedom, privacy and security.
This is exactly what Free Software is about.
Then, they start banning GPLv3.
Next, the same "Linux is cancer" microsoft now "loves Linux" and buys GitHub.
The EEE process is going strong.