Qownnotes

It’s a desktop app, but can sync with self-hosted cloud servers. It’s also literally just text/markdown files.

For sure, but as long as clickbait works they’ll keep doing it.

To be fair, “an entire x” does have markedly different connotation than “x”. The emphasis is that it’s, well, the entirety of x. It’s the difference between “i ate the cereal” and “i ate all the cereal”.

I mean to be fair, those errors arent really meant for you (the end user) in the first place.

it makes what looks like formatting an arbitrary complex operation and that it doesn’t improve readability that much.

What’s silly to me about that reasoning is that all workarounds are equally less convenient, have less readability, and the effect is identical to just letting me put whatever between the brackets. I genuinely dont understand the downside i guess.

Calling .join on a vector can have side effects too, except the “we’re concatting strings” is at the end rather than the beginning (and could obfuscate the fact that the end result is a string). It has just as much room for abuse as a long format!(). Even with just format!(), anything you could do inbetween the brackets, you can do outside the brackets in the arguments anyway. At least when it’s between the brackets, i know exactly where it’s going and when without having to juggle the string pieces and assemble them in my head.

in this case it’s about 80% function calls. They’re convenience functions for assembly instructions, so they’re of the form:

load(Reg::D, "A"),
load_const(5),

which is more useful than variables would be. I guess i could use .join or a crate like concat_string? Either way i sorely miss arbitrary expression format strings from python =(