I've seen that C# and Java do have this kind of logic. I've also spent a few seconds to read the blog post from brent.
Yes, there are use-cases where default methods might be helpful. But the same argument given in the blog post regarding "how many implementations will look other than..." can be given with "how many interfaces have this kind of abstraction".
So how many default methods will be around if we support this kind of "feature"?
If that only applies to LoggerInterface
since its design allows us to easily provide default methods, I don't see a benefit here.
Most interface methods are usually not simple proxies to other interface methods and thus thats barely useful.