At some point, the results of what the side process did have to get communicated... | Hacker News

Hacker News new | past | comments | ask | show | jobs | submit

login

yuliyp on Dec 11, 2012 | parent | context | favorite | on: How a load-balancing bug led to worldwide Chrome c...

At some point, the results of what the side process did have to get communicated to the parent process. You can reduce the size of the channel, but you can't close it completely. Bugs happen. Bugs in never-executed code happen and tend to stick around longer.

azakai on Dec 11, 2012 [–]

> You can reduce the size of the channel, but you can't close it completely.

Of course, no one would argue otherwise. Every time you decide how much to reduce it, you define a tradeoff in terms of work vs. benefit.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact