A small gui to automate generating some pdfs from some CSV files.

There’s a small non-profit in my area helping people operate localized energy distribution (as producers and consumers). Each month, they receive a zip file containing the raw kiloWatt-hours produced and consumed by each participant over the past month as CSV files. So far the non-profit has been manually importing these CSVs into LibreOffice to generate graphs and tables and export the whole thing as an individualized PDF file for each participant. Now that they’re starting to help more than 2-3 operations, it’s become useful to try to automate that process.

I’ve been writing it in rust for a few reasons. First of all I wanted cross-compilation to be sure to work and at this point I’m more familiar with rust than go, secondly I read a blog post recently that evaluated rust gui solutions in terms of accessibility and IME-compatibility on windows. I started off looking for a “direct” pdf-writing library but eventually switched to using typst to generate the pdfs from templates I write. typst being written in rust has enabled me to bundle its engine into the program in a pretty-straightforward way.

I’m currently working on allowing the import of multiple sets of data so that the generated PDFs can show line plots of the electricity production and consumption over several months.

1. chunk_size := file_size / cpu_cores. Compile regex.

2. spawn cpu_cores workers:
   2.a. worker #n starts at n * chunk_size bytes. If n > 0, skip bytes until newline encountered.
   2.b worker starts feeding bytes from file/chunk into regex. When match is found, write to output (stdout or file, whichever has better performance). When newline encountered, restart regex state automata.
   2.c after having read chunk_size bytes, continue until encountering a newline to ensure the whole file is covered by the parallel search.

Optionally, keep track of byte number and attach them to the found matches when outputting, to facilitate eventually de-duplicating and/or navigating to said match in the file.

To avoid problems, have each worker output to a separate file, and only combine these output files when the workers are all finished.

As others have said, it’s going to be hard to get more speedup than this, and you will ultimately be limited by your storage’s read speed and throughput if the whole file cannot fit into memory.

For those on Android, check out Imagepipe on f-droid. It’s got a workflow that I really like: "share"ing an image to it automatically strips metadata and re-triggers the “share to which app?” Android prompt with the stripped image file instead of the original.

Counterexample of one, but I’ve commented in womensstuff before as a genderfluid person and have not been asked to leave the space.

From what I understand, it is the arch approach but with package binaries compiled to target newer hardware instead of the largest set of hardware. Their homepage claims they enable several performance-type optimizations in both the kernel and common system libraries. It’s not surprising to me that protondb, a repository of “how well can I get this game to run on Linux through proton?” reports, is studying an outsized proportion of users on CachyOS.

1893: the US air force guess back in time to pull the ultimate prank on it’s older siblings

It’s not chatbot psychosis, it’s ‘math and engineering and neuroscience’

top-tier sneer from The Register

You can use me after free() all you want, babe

always nice to see a wholesome meme

Then there’s kids like me, who would daydream about actually being a fae changeling.

It’s not even as if my parents didn’t love me, I was just a weird kid who was more comfortable being weird than fitting in.