miniblog.

When a tool supports both regular expressions and literal strings, which should be the default? If you default to regex, users can match more strings than they realise (e.g. `foo.txt`) or less (e.g. `foo(bar)`). I typically see regex as the default, but I prefer the opposite.

It's always seemed odd to me that the Rust stdlib is so lean (no random numbers, regex, HTTP) yet clippy is so big (correctness, performance, style preferences, even 'too many arguments'). Maybe it's because cargo is mature but clippy doesn't have an extension ecosystem?

Seen in the wild: replace all the newlines with a literal $ in sed: sed -e 's/$/$/' It's always bugged me that regex replace syntax looks similar to regex, occurs close to the search syntax, but actually has a different meaning. It's harder to read.