Why does java have so many nonsensical limitations? Why? Why can't we have multiple heritage? Why can't we have friend classes? Why can't we make static abstract methods? Oracle, PLEASE.

Honestly with my experience with C++ and working with it I think that multiple heritage and friend classes should be avoided whenever possible

Multiple heritage is to be avoided like the plague actually. It creates more chaos than order in large projects and there are way better solutions for it.

If you have multiple heritage then you dont understand oop at all

You can "sort of" have multiple inheritance by implementing multiple interfaces

No idea what friend classes are, so can't comment on that

Static abstract methods...just don't make sense? In what situation would you want to use one?

Java wants to protect you from making mistakes.
It may be tedious sometimes, but in the end it helps you alot.

Juat look at how much shitty code ia written in dynamic weak type languages like Python, js or ruby and you will understand that Java does this for a reason

@HenryCGS, it seems you have very bad models and designs and n your head, that you may want to fix post haste!

@Ezard they are basically same package classes that shit on security and have access to the other one's private stuff

@BindView Isn't that what package access modifiers are for though? (aka default)

@Ezard yeah, its basically the same as 'protected'

But im not a c++ pro by any means so dont take my word for granted