I too have encountered this headscratcher.

I would be happy to change it if it is something that we can agree on.
Hens I opened an issue first because I thought there might be some thought behind it.

I looked on a git blame and it came from MZ direct commit.

I remember discussing this with @warp-core at one point. I recall at the time that my idea was to flip the inheritance, although we figured there would be issues with that. Instead changing to composition as you described would likely be the better option.

Yeah same I'm confused
I can understand why ships are outfits but this is weird

For sure something to do!

So I was trying to implement something

@warp-core would like to know what it was that you were attempting to implement. And from the PR:

Usage examples
makes some changes a lot easier

What changes?

@warp-core would like to know what it was that you were attempting to implement

I was trying to add more than one weapon node to outfit to create a double effect gun or a gun that shoots two different projectiles that are not timed the same way, which is difficult to do with sub-munitions especially the timing thing

What changes?

refer to the top
changes that require you to use weapon as a separate object from outfit, fr example multiple weapon nodes or maybe even a gun that can use different types of ammo but that would be even more complex

Cant we just have 2 weapons taking the same turret mount? (And you'd be surprised what you can do with submuns)

Ye but no? I want an outfit that shoots two things not a dual turret mount, thats something different no?

(And you'd be surprised what you can do with submuns)

Yes but we can also just make things easier