I've been always using -r for grep so it never occured to me that such a thing could happen

Looks like user error to me tbh, similar to `rm -rf /`. Should `rm` give a warning when / is the argument?