Lennart Poettering on Nostr: When pondering whether we should start linking to some external library in systemd, I ...
When pondering whether we should start linking to some external library in systemd, I usually spend some time looking at the library's sources, to understand the quality of the code. While coding style differences are fine, there are certain red flags that make libraries unsuitable for use in systemd, or that indicate questionable quality of the code.
Red flags like this are for example absence of OOM guards on malloc(), absence of reasonable error propagation,
Published at
2024-05-28 09:15:16Event JSON
{
"id": "a9385648ff19f082f54b1917e358e5633524cbb1bfe73ec9c50c7edb30f9eccf",
"pubkey": "1d95c32d9a9d95a54f98eb2eaa156f3d3a71dc49eca2c960b2b89962758f1cc0",
"created_at": 1716887716,
"kind": 1,
"tags": [
[
"proxy",
"https://mastodon.social/users/pid_eins/statuses/112517953375791453",
"activitypub"
]
],
"content": "When pondering whether we should start linking to some external library in systemd, I usually spend some time looking at the library's sources, to understand the quality of the code. While coding style differences are fine, there are certain red flags that make libraries unsuitable for use in systemd, or that indicate questionable quality of the code.\n\nRed flags like this are for example absence of OOM guards on malloc(), absence of reasonable error propagation,",
"sig": "9d0c1a6127c04d48a2323a7fa5e81e0a30eac9372f5914d2f252aa61a4834e07dd2c80a1d2c42cbae09d1938081f130b7156b61438aa705c2afbe360839a61f1"
}
