This started off as a single file in my private nix config, to see if I could get it working at all. In that initial part, some parts were indeed LLM generated (esp. testcases based on my existing intents and failures).
When I noticed that this might actually work and be useful not just for myself though, I moved everything out manually, refactored and cleaned it up, and everything since has just been myself. I guess you're still right though. I'll see about adding a disclaimer to the README until I've gotten the chance to properly rewrite everything.
I did not even know about this. Sounds super interesting. Though it seems to be very language specific?
My original intent was to not rely on language specifics. But maybe we could just define additional steps in the pipeline for specific languages. Hm. I'll have to think about this some more, but it might definitely be a great idea for a future version, so thanks for telling me about it!!
Have fun, hope this works out for you! FYI: you can also use an LLM as an additional fallback (first closest-intent, then on failure, LLM). README mentions it further down on Github.
I bought a Brother HL-L2375DW a couple of years back specifically for Linux compatibility, and it did NOT disappoint.
haven't had a single error
has not refused to print a single time
super quick, good quality, duplex
using cheap 3rd party toner without complaint
works perfectly from Linux
I don't usually like to recommend brands/products, but this is the exception. If you need a printer, and black and white is all you need, go for this one.
Maybe the underlying rule is: the more you know about something, the more you are aware of its flaws, making the alternatives you know less about more attractive?
I went with continuwuity and am happy with it. Development happens at a steady pace, with sane priorities. The server is stable and I haven't had any issues to speak of, despite one minor bug that got resolved very quickly after creating an issue.