限定的な読み取りを許可するプロセス間リーダー/ライターロックの開発、パート3：公平性

排他取得（書き込み）が共有取得（読み取り）に対して公平に競争できるようにする方法について解説します。本記事は、複数プロセス間で動作するリーダー/ライターロックの実装シリーズの第3回目です。

Notes on structured concurrency, or: Go statement considered harmful (2018)
5.5
The article argues that unstructured "go" statements cause concurrency bugs and proposes structured concurrency as a safer alternative, where concurrent tasks are nested and scoped to make lifetimes predictable and prevent resource leaks.
Registries Considered Harmful
5.0
The article argues that centralized package registries (like npm, PyPI, etc.) introduce security risks, single points of failure, and governance problems. It advocates for distributing trust through cryptographic signatures and transparency logs instead of relying on a central authority to vouch for package authenticity.
The Harmful Consequences of the Robustness Principle (2018)
3.5
The document argues that the Robustness Principle ("be conservative in what you send, be liberal in what you accept") has harmful consequences for Internet protocol design. It contends that accepting malformed inputs leads to interoperability failures, ossification of protocols, and security vulnerabilities, advocating instead for strict validation and clear specifications.
Consequences of passing too few register parameters to a C function
1.5
This article discusses the undefined behavior that occurs when a C function is called with fewer register parameters than it expects, explaining how mismatched calling conventions can lead to reading garbage values from registers and causing unpredictable program crashes or data corruption.

翻訳言語

Notes on structured concurrency, or: Go statement considered harmful (2018)
5.5
The article argues that unstructured "go" statements cause concurrency bugs and proposes structured concurrency as a safer alternative, where concurrent tasks are nested and scoped to make lifetimes predictable and prevent resource leaks.
Registries Considered Harmful
5.0
The article argues that centralized package registries (like npm, PyPI, etc.) introduce security risks, single points of failure, and governance problems. It advocates for distributing trust through cryptographic signatures and transparency logs instead of relying on a central authority to vouch for package authenticity.
The Harmful Consequences of the Robustness Principle (2018)
3.5
The document argues that the Robustness Principle ("be conservative in what you send, be liberal in what you accept") has harmful consequences for Internet protocol design. It contends that accepting malformed inputs leads to interoperability failures, ossification of protocols, and security vulnerabilities, advocating instead for strict validation and clear specifications.
Consequences of passing too few register parameters to a C function
1.5
This article discusses the undefined behavior that occurs when a C function is called with fewer register parameters than it expects, explaining how mismatched calling conventions can lead to reading garbage values from registers and causing unpredictable program crashes or data corruption.

関連記事