It really isn't optional as a C developer to turn on warnings and get your code warning-free. This will eliminate the most common unbounded behavior issues, like uninitialized variables, though unfortunately not all of them.
All the arguments in favor of regenerative meat production that I have heard consider, and in fact stress all these issues. Your link was a technical debate about soil carbon storage, (which I suspect regenerative ag proponents would dispute the details of, which would be an interesting thing to get to the bottom of). It doesn't at all cover any of those other more important topics you brought up in this quote. Anyway, a smart guy citing his chosen evidence in a public debate hardly settles any issue either way.
>> no science exists supporting your claims
this is hyperbole, and easily disproved by a quick google search.
which says also:
"The new peer-reviewed study looks at the multi-species rotational grazing done on the ranch and found that White Oak’s approach reduced net greenhouse gas emissions of the grazing system by 80 percent. Regenerative practices helped sequester 2.29 megagrams of carbon per hectare annually. To put that into context, sequestering just 1 Mg of carbon per hectare each year on half the rangeland area in California would offset 42 million metric tons of carbon dioxide equivalent, roughly the annual emissions from energy use for the state’s commercial and residential sectors."
So even if it is legal to create a commercial product which outputs GPL code as its main value-add, it still seems like it could put the user in an awkward position of auto-completing big chunks of GPL licensed code into their project.
I believe this piece does a good job with forwarding, but would be improved by a discussion of termination.
Routing is only triggered when the packet is L2 terminated: the destination MAC of the packet is one of the router's own MACs.
If the packet's destination MAC does not belong to the router, it doesn't matter what is in its IP header, it will be switched in the LAN it came in on.
This design also generalizes nicely to the case when the destination IP of a routed packet is one of the router's IPs.
Good point. Incorporating that would require more brain that I have right now (bad timezone :D), but you're right, I completely left that out. May I update the article with a link to this comment?
In the free society I want to live in, we ought to let people voice their opinions even when we disagree. There are limits to freedom of speech besides those put in place by the state.
Taken to an extreme for purely rhetorical purposes: if you get fired, black-balled, and publicly shamed for voicing any opinion, then do you live in a society with freedom of speech?
If you live in a society where thoughtful, rational discourse is drowned in a sea of shouted opinions, then you do not have free speech either. Free speech is not the freedom to say anything you like, but the freedom to express any idea you like. You are not free to express it how you like to whoever you like.
And there aren't many liberals willing to censor people for controversial opinions presented in a self-aware, carefully worded, and relevant manner abounding in due consideration for the facts. They do censor people who like to peddle propaganda and wave their victimhood around like pariahs.
Perhaps I'm misunderstanding the second line of your post, so I apologize if that's the case, but the whole idea of the PID namespace is so that the container's init can run as pid 1 in the container without access to the rest of the host's processes. Likewise for root and user namespaces. (Though I understand that one is really tricky to get right)
What about the fact that tons of people can afford super nice things today by the standards of even 20 years ago? Imagine going back in time 20 years and showing somebody the iphone 4. Or going back 100 years and showing them the beat up junkers people drive in India. Both of those would be miracles, and yet today are very affordable.
