Skip to content

Modularization/moving implementation away #19

Description

@Olafcio1

Avoid does not fully utilize OOP, therefore interfaces cannot fully replace pure classes/records/enums/whatever it is in Avoid, without breaking compatibility. I also do not want to fully utilize OOP as it would create more problems and wasted time than actual fixes.

I tried using Gradle submodules, however they cannot depend on each other, therefore I hate Gradle yipee

For real though I am tired of this shit I accidentally push out a release that uses fucking mojang datafixer Either instead of idk apache commons or something. And I can't separate shit into modules because everything depends on each other. It's not fucking my fault, it's how games are designed, no? I'm not going to rethink the whole Minecraft architecture to make it "better".

So yeah I can't do shit. Because even if I separated it within a single module (main), that'd make no sense. Because I still would be able to import Minecraft shit in the public API-s. So like what?

Edit I guess Gradle comm told me it's possible so I guess I might try that out soon i don't know

gradle/gradle#39000

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    internalThis issue is related to internal AvoidLib concerns.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions