once again, i am stating this is THE PREMISE of the fighter not THE EXECUTION and considering the following is part of the fighter's class description i am very much in question about 'not even thematically'
That is a far cry from your description.
i am saying that classes like paladin, ranger and barbarian are classes of 'someone who fights', i am saying that for fighters fighting is a way of being, the argument i think is happening is that you are focusing too much on the mechanical capabilities of the fighter being so similar in comparison to the mechanical capabilities of other classes rather than the conceptual essence of the fighter where they should be far superior at combat.
Paladin, Ranger, and Barbarian, are
Warriors. The fight is the point of them. Literally the point of Paladins is the fight against “evil” or the enemies of thier god, the point of Rangers is the fight to keep civilization from getting eaten by dragons or whatever, the Barbarians point is
just to fight. It’s the whole identity of the class, they’re The Primal Warrior, to the Fighter’s The Civilized Warrior.
As for the mechanics, this whole exchange is about the classes as they are. I’ll ignore execution issues, but they didn’t even actually try to make the fighter a totally different category of thing from other warriors.
If you can put a divine knight subclass on the fighter and do the Paladin’s thing without issues, that is a fault in the Fighter class, not the Paladin. The Fighter should have enough identity that it interferes, at least a little, in modeling another classes tropes.
I objected to the notion that you could just dump all the other warriors into the fighter and have a class worth playing, saying that instead I think better outcome would be to split up the fighter and let it’s features be used by different classes.