boryas

linux, qemu, postgres and many other projects written by "C developers" use and rely on fwrapv, fno-strict-aliasing and others.

-fwrapv and it's all good :)

>> biodiversity loss, deforestation, eutrophication/pollution, pesticide/herbicide use, ethical concerns etc

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.

"white oak pastures debunked", to avoid finding biased pro-regenerative papers, links to an anti-regenerative writeup: https://civileats.com/2021/01/06/a-new-study-on-regenerative...

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."

CoPilot has been demonstrated to lift code verbatim (including swearing comments): https://twitter.com/mitsuhiko/status/1410886329924194309

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.

LLVM e.g. SmallVector: https://llvm.org/doxygen/SmallVector_8h_source.html

Folly e.g. https://github.com/facebook/folly/tree/master/folly/logging, https://github.com/facebook/folly/blob/master/folly/concurre..., https://github.com/facebook/folly/tree/master/folly/executor...

sure!

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.

> where does most packet loss occur

Here's an interesting paper from SIGCOMM (it won best paper at the conference in 2018, FWIW) that attempts to figure out what links are congested without direct access to ISP networks: https://www.caida.org/publications/papers/2018/inferring_per...

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?

https://en.wikipedia.org/wiki/On_Liberty#Of_the_liberty_of_t...

First line of the Go announcement: "Go is building a garbage collector (GC) not only for 2015 but for 2025 and beyond"

to me, that suggests they think they have the future of GC

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.

because it's his money

I'm sure your billion person social app is killing it due to awesome optimizations baked in from day one. Nicely done.

How big of an expert on deserts do you have to be that Dune stops being interesting? Unless you still find it valuable emotionally or philosophically and just reject is as 'science fiction' I think it's a bit sad to just flat out get rid of such an interesting book!

make_shared and make_unique http://herbsutter.com/gotw/_102/

I was sure it was going to be Key Lime Pie

Doesn't the blkio cgroup not know anything about buffered writes? Or do the shares work differently and that limitation is only for accounting?

Guess: maybe all the pointers to structs are typedef-ed away?

Holocaust denying? Really?

yes, using the "intenet"

I'm surprised this is missing the canonical quicksort in one line of Haskell

what python code should people write for non-constructive results?

After a point, but I think a large part of getting a problem is committing maximal time and energy to solving it or "dying"

For this reason, take home exams are evil. Also, get rid of the fourth strategy

I'd like to extend his position to the argument that the semantics of any language that isn't ML or Lisp are too complicated...

As an alternative to tau, I propose the symbol 2*pi.

Yeah, well, you know, that's just, like, your opinion, man.

How can you know that driving isn't fun if you don't have a license? There are many people (e.g. all of Finland) who find it quite fun :)

With regards to List.map: List.rev_map is also in the standard library and is tail-recursive, so you can just do List.rev(List.rev_map l) to tail recursively map. Just had to defend Ocaml a little :)