herne
Re:A look at Chrome’s security review culture
on Monday July 24, 2023 @06:41AM (#36845682)
That would be a great companion post, the process this one describes doesn't include code review per se.
Re:Checking It Twice
on Monday September 20, 2021 @05:43PM (#28599389)
I ended up with this in my .bashrc so I didn't have to keep remembering how to use comm each time:
justA() { comm -23 <(sort -u "$1") <(sort -u "$2"); }
justB() { comm -13 <(sort -u "$1") <(sort -u "$2"); }
bothAB() { comm -12 <(sort -u "$1") <(sort -u "$2"); }
Re:Google Chrome’s new Meltdown and Spectre safeguard is a memory hog
on Saturday July 14, 2018 @11:56AM (#17530811)
The article didn't link to the actual blog post:
https://security.googleblog.com/2018/07/mitigating-spectre-w... which has some more nuance:
"on the plus side, each renderer process is smaller, shorter-lived, and has less contention internally, but there is about a 10-13% total memory overhead in real workloads due to the larger number of processes"