I believe some of the Geode community has already decided that we shouldn't
overuse default methods in interfaces. Dan and others were the ones who
decided this and thus I can't really explain to folks in PRs why it's bad
to overuse default methods. Could some of the folks with strong
understanding of why we should avoid making every method default empty
please speak up here and/or in https://github.com/apache/geode/pull/5014?

My understanding is that default implementations should only be provided in
interfaces when it's important to do so for facilitating some sort of
deprecation and replacing a deprecated method.

Thanks,
Kirk

Reply via email to