Java has its own problems with generics, such as the near-lack of runtime representation or the lack of a This/Self type, as well as limited variance, leading t

Java has its own problems with generics, such as the near-lack of runtime representation or the lack of a This/Self type, as well as limited variance, leading to signatures like `public abstract class Enum<E extends Enum<E>>`. IMHO these all go back to design compromises due to the desire to make generics optional - but now, over two decades later, are Java generics really optional? The ten levels of parent classes is its own issue with Java - with interfaces and class inheritance being a good half of your mechanisms for abstractions in the code base, with adapters making up the other half.