I looked into the lemmy src, and what is supposed to be a CRUD API has several layers of abstraction. Same at work, where we have hexagonally structured apps where following any sort of logic is literally impossible. What are your thoughts?

  • Stumblinbear@pawb.socialEnglish
    4·
    1 year ago

    I just had a look at the Lemmy source and it seems pretty straightforward, what exactly are you having issues with?

      • key@lemmy.keychat.orgEnglish
        4·
        1 year ago

        I don’t see the problem with modularizing code. Any proper IDE will make following through the crates as transparent as if it were all in the main src folder. It’s not like there’s some complicated indirection at play or anything, it’s direct references and invocations.

          • recursed@lemmy.recursed.netEnglish
            2·
            1 year ago

            Given this project has been around for many years, (looking at their releases), I wouldn’t say it’s “early” to modularize their code. It’s very common practice to abstract out / move commonly executed code into their own packages and modules to allow ease of reuse across the app. This way if an entire subpackage needs to be moved or deleted, all related code could be affected at once and code which references it, simply needs to be edited. Typically these places to edit are much easier to handle since most of “calling code” wouldn’t touch the modularized / abstracted code, only their callables.