This is the kind of thing that makes cursive painful to read. The `i` and `j` in this script are harder to quickly lex, and the `t` (especially in the `tt` ligature) with the added loop flourish diverges sufficiently from a standard `t` to make it hard to decipher in running text.

In text, as in code, I prefer to optimize for easy reading rather than faster writing.

This reminds me of build-time optimizations increasing compile times for faster performance at runtime. A tradeoff I could make without a sweat in prod, but not so much during development, at a certain scale. It feels like a dichotomy almost unavoidable in life.

I read the backtrack free "pretty" as "pretly" at first; it adds cognitive load to understand it as intended.