Hello Ali,
Thanks for bringing this up.
We design KStream and KTable to not extending the same base class
intentionally to now allow these classes to be used exchangably or
polymorphically
by design, since their semantics are different for those same-named
methods, for example joins and
They both have a lot of the same methods, and yet they can't be used
polymorphically because they don't share the same parent interface.
I think KIterable or something like that should be used as their base
interface w/ shared methods.
