iliana

pure of heart and dumb of ass

computer toucher (derogatory); recreational bureaucrat; longer intro


ktiiy, full-stacked shitpost development engineer, and crow appreciator


get shrdled, idiot


see also:


blog / RSS
iliana.fyi/
email me
iliana@buttslol.net

i think i am frustrated with my current task at work because neither rust nor bash are really the right fit for this tool.

i need a more ergonomic rust: one that does not require me to manually attach a filename to every std::io::Error that i want to tell the user about, so that they don't tear their head out seeing "errno 2" for the ninth time that week; one that lets me describe the delicate stack of cards i have stacked atop the user's filesystem and lets me describe a set of teardown tasks without having to impl Drop and deal with async-vs-not-async; one that lies to me about the subtle differences between what filenames are allowed to be and what UTF-8 is allowed to be

i need a less fragile bash: one with structured errors and better handling; one with a real command line parsing utility, instead of while (( "$#" )); do ... shift ... done; one with logging that is less stupid than the false "is this to be piped into a program" vs "is this an error" binary

i need a rash. or a bust. wait i have both of those


You must log in to comment.

in reply to @iliana's post: