Indeed, it's something where we lack consensus across languages and sometimes within the same ecosystem.

A couple of flaws in this article I think. For instance, the benchmark part looks fishy to me. Also it's a bit opinionated and goes too far in advocating exceptions at the expense of error values.
Still, I think it shows quite well that we can't do without exceptions at all, even in the case of error values being available. In my opinion, we're still learning how both can be cleverly used in code base.

Definitely this, it's been tried in Java, now we know it was a bad design decision... but it had to be tried to realize it.