Rename Modstitch to... `modstitch`

[Kira-NT]

This is more of a styling issue, but I really do think that the main plugin should be called modstitch instead of modstitch.base. The current state of affairs isn't great: neither from the external perspective ("Why do I have to apply the modstitch.base plugin and not just modstitch?"), nor from the internal one - things like BaseCommonImpl are bound to appear in some upcoming hitpiece on how OOP is gonna kill us all, which seems to be a popular topic lately.

Renaming the main plugin to just modstitch should have a positive effect on both user and developer experience: it will be easier for people to remember what they need to install, and easier for Modstitch developers and contributors to make sense of the codebase if it uses slightly more sensible naming :D

As always, if you're OK with this suggestion, I'm happy to turn the issue into a PR :3

[isXander]

When I made this plugin it made sense that each feature is compartmentalised. The idea being you have this minimal base plugin and you compose needed functionality on top.

plugins {
  id(“modstitch.base”)
  id(“modstitch.mixins”)
  id(“modstitch.kotlin”)
  id(“modstitch.shadow”)
}

I think the base plugin has slightly overgrown its original scope to be honest.

There’d be other convenience plugins that would apply a set of these like modstitch.defaults.

Maybe it makes sense to make base into just “modstitch”, but it makes the abstraction more complicated and confusing in my opinion.

What’re your thoughts?

[Kira-NT]

Oh, I see what you were going for. Moving components that alter the build process in ways that might be unwanted by the user (like shadow) into separate plugins does seem like a good idea. However, I don't quite see the point of creating separate plugins for every minor essential feature (like mixins, accesswidener, etc.) only to unify them again through a defaults package that 100% of users will end up using anyway. That feels a bit contradictory to your stated goal of reducing boilerplate.

I believe the main modstitch plugin should be capable of handling a typical setup entirely on its own. Extension packages (such as modstitch.shadow, modstitch.kotlin, and so on) should only be created when they affect the build process in a way that might be undesirable for users who don't need those features, or when they diverge significantly from Modstitch's core philosophy.

[isXander]

Completely agree here.