> not using unneeded classes makes your code harder to read for many colleagues This would be really depressing for me but ultimately team limitations sometime

> not using unneeded classes makes your code harder to read for many colleagues This would be really depressing for me but ultimately team limitations sometimes win out. If your team can only "understand" code that looks like Java, then maybe all code has to look like Java. In white collar environments, "don't understand" can be a sneaky, faux-polite way of saying "don't like and refuse to be open to". But it might add up to the same thing in the end.