Ended up installing Rust manually, the way I'm accustomed with (copying files independently to /usr/bin and /usr/lib as my Arch Linux is out-of-date as hell (because I need a new 2.5" HDD for my laptop but, if I couldn't afford one back when I began needing one, the situation is even worse now as computer parts are more expensive "thanks" to OpenAI et al) so I must install manually, which often works unless the program required a newer Glib version) and an pacman -S rust won't likely make ip), after reading the install.sh that comes with the "not-recommended" Tarball version.

This is the first time I'm dealing with Rust because I had to compile and run a project called "aero530/SketchbookTiffConverter" which, well, it's quite of self-explanatory (converts a Sketchbook TIFF file, which is the project file containing layer information for digital drawings).

Yeah, it worked (also TIL about .ora "OpenRaster" image file format; it's yet another XML in disguise, though...) as you can see in the screenshot.

I'm thinking of implementing this "skora" in JS, so it could run in a browser and use HTMLCanvasElement to view and export layers on-the-fly (currently, it seems to be generating a single file). However, before I do this, I'm trying to learn how Rust works by trying (trial-and-error) to modify the original SketchbookTiffConverter project, adding a PNG output feature to it...

Oh, and fwiw: without using AIs because I want to understand the source-code instead of simply doing a functional thing... and also because I'm quite outdated to modernity and don't really know how to setup a proper coding AI environment (you know, the "CLAUDE.md" thing and its equivalents for other LLMs, I don't know how I'm supposed to configure such a thing), and between having to learn how to setup a modern AI coding environment or having to learn how a Rust source-code is working using the manual environment (a text editor with a crude auto-completion feature running on my decade-old laptop...) I'm already used to, I'm obviously leaning towards the latter because, well, I used to be a developer and despite having abandoned my devops career, it's quite of a muscle memory.