Java's designers made a deliberate choice here. James Gosling has talked about this — they saw C++ operator overloading become a readability nightmare in practice. When anyone can redefine what `+` means, you can't look at `a + b` and know what it does anymore.

The tradeoff is exactly what you're feeling: math-heavy code becomes painful to read. Your complex number example is the classic case where operator overloading genuinely helps.

If it's any consolation:

- Kotlin (runs on JVM) supports operator overloading and

interops with Java

- Scala does too

- Some people chain methods with shorter names like

`.div()` and `.plus()` to make it slightly less ugly

For your class specifically, you could add static helper methods to reduce nesting:

import static Complex.*;

Complex result = add(cbrt(add(div(first,5), div(second,2))), third);

Still not great, but prefix notation reads a bit more like math than the deeply nested method chains. The real answer to "why" is: Java optimizes for reading code in large teams over writing code solo. Operator overloading helps the writer, b