A link to the commentary asks me to share my data with their 165 partners. I find it ironic.

> A link to the commentary asks me to share my data with their 165 partners. I find it ironic.

I guess this is the issue here. For some, data collection, is just _ironic_. /s

I had to double check if posh isn't some of 1st April RFC

This is from February 2022. This should be in the title.

It's in the article. You should read it.

tl;dr - healthy individual without family history could be more likely to refuse the screening (less refuses were diagnosed with CRC than the control). This is the reason the study can't omit refuser from calculations.

It's like a communist party opens a dam or a factory earlier just because it's the party's anniversary.

... | xargs grep -Hn regex

This will also be faster, because you fork less.

Using \+ instead of \; will do the same (fork less).

du -a will need to do a stat to get the file size, which is comparatively expensive; I don't think find will (not sure)?

You're right, find won't call stat() unless it needs to. It doesn't need to for recursing through the directory tree because readdir() returns dirent.d_type these days to determine if a name is a directory.

Yes, those stat() calls can be very slow in aggregate on a large tree, especially from HDD (due to seeking) or network filesystem, if the stat information isn't already in cache.

Oh, I forgot about \+. I still pipe to xargs every single time.

Does this deal with arbitrary filenames (having newlines, control chars etc) correctly? Or does Plan9 forbid such filenames?

I've never used plan9. In Linux you do "find -print0 | xargs -0" to deal with that.

Im not sure how one can do \0 separator with du, plan9's du(1) doesn't list such option.