Makes code more readable because has the natural direction of reading (if reading left-to-right, of course)
An interface defines... well.. just an interface. Not the implementation.
The feature of having default implementation is kind of already there: just use traits or abstract classes. Having any implementation in the interface makes the code blurry. When can I rely on an interface being totally a pure interface, when is it half-interface with some implementations?
It opens also a way for introducing new behavior and automatically populated to all implementations. Even to implementations where the default behavior would be plainly wrong. Wonder if my tests would show any sign of something being wrong. If I did my code based on an interface, like a contract, suddenly the contract could change without me noticing it.