From c6ff2e34665ab72a8e460b0e08745509c6500233 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?nep=C3=A8ta=20dyengxuah?= Date: Wed, 9 Apr 2025 00:03:20 +1000 Subject: bring shit back in --- blog/2023-09-30-computing-dystopia-part-1/index.md | 28 ++++++++++++++++++++++ 1 file changed, 28 insertions(+) create mode 100644 blog/2023-09-30-computing-dystopia-part-1/index.md (limited to 'blog/2023-09-30-computing-dystopia-part-1/index.md') diff --git a/blog/2023-09-30-computing-dystopia-part-1/index.md b/blog/2023-09-30-computing-dystopia-part-1/index.md new file mode 100644 index 0000000..3893cd6 --- /dev/null +++ b/blog/2023-09-30-computing-dystopia-part-1/index.md @@ -0,0 +1,28 @@ +# computing dystopia: part 1 + +hi. on my server i run a javascript-based daemon +(its function is irrelevant here). +i also, seperately, run the rss fetcher +[`sfeed_update`](https://codemadness.org/sfeed.html) which i then +transfer to my laptop where i read it. + +today i noticed my feeds did not seem to be fetching. weird. +after like a minute of investigation i find that my `/tmp` directory, +kept on an 8GB ramdisk, had run out of space... +but what could be causing it? + +so it turned out that my `/tmp` directory was filled with temporary +directories created by the javascript package manager(?) `yarn`, +which would create a new directory every few seconds. + +so i find a github issue about this, open since *november 2018*, +which contains no solution other than running a cron job or +changing to `yarn v2`, which my daemon does not seem to support +and distro does not package. + +of course, while this massive issue affecting quite a few people +is not worth fixing after five years, it is important to hide +a comment, labelling it 'unprofessional' and 'not worth visibility' +for containing a silly image in it. + +writing software in javascript is immoral. -- cgit v1.2.3