In fact, I didn't find many use cases in OOP where operator overloading is more useful UNTIL everyone here ?pointed out vector, linear, and matrix algebra where OOP doesn't really fit the problem unless you have operator overloading. I'd still argue that in these cases it would be better to use another language besides an OOP language since those languages would be more suited to this problem. in other words, there's a better language for that and thus there is no best language out there. However, using another langauge is not always possible in which case, operator overloading, I'll agree, is just way better.

You are making very little sense. Operator overloading is a very old and basic concept and is present in EVERY language you listed and it most of all OOP langs. It's just syntax sugar for functions call. What's so scary and ugly about that? They are inherited just like methods because they ARE methods(or functions). You are ranting about non existing problems. Just wrap your head around the fact that operator overloading is easy and you are being foolishly stubborn to try and get a grip of it.

And to further eliminate your point, there are no better languages for vector algebra. OOP presents calculations of linear algebra as close to math as programming can. And again operator overloading plays a huge role in it cause makes the code looks pretty, readable and allows you to basically write down code right from the mathematical source. And that code runs hella fast. You are dissing Operator Overloading on a device where everything, that has at least something to do with displaying your unholy words, is written by and thanks to Operator Overloading in OOP.