In Scala, the debate between using fold on an Option or using map and getOrElse is almost as old as the language. The method signature for this is:
def fold[B](ifEmpty: => B)(f: (A) => B): B
def map[B](f: (A) => B): B
def getOrElse[B](f: => B): B
You make the Understanding This Codebase 101 curriculum some percent longer without making your programmers any better.
If it's terseness, I don't really think one symbol is any verbosity benefit over two. Same order of magnitude, same cost. It's a rounding error in brevity. People way overvalue terseness.
And the cost of people missing chances to learn getOrElse has got to be massive.
It looks like syntactic sugar here, but it's really not. It's just a function that is more commonly used on collections with more than one item.
 also reduce, inject, aggregate, and other synonyms, because naming is hard