▲ 81 ▼ Are monorepos really simpler? (www.youtube.com) submitted 8 months ago by jeena@piefed.jeena.net to c/programming@programming.dev 28 comments fedilink hide all child comments
[–] majster@lemmy.zip 10 points 8 months ago (1 child) Agree with this explanation. Also in a monorepo it's much easier to reference code between modules and I think this leads to too much coupled code. It takes more discipline to limit the scope of modules. permalink fedilink source parent hideshow 2 child comments replies: [–] pupbiru@aussie.zone 1 point 8 months ago* that’s a good and bad thing though… it’s easy to reference code, so it leads to tight coupling it’s easy to reference code, so let’s pull this out into a separately testable, well-documented, reusable library my main reason for ever using a monorepo is to separate out a bunch of shared libraries into real libraries, and still be able to have eg HMR permalink fedilink source parent
[–] pupbiru@aussie.zone 1 point 8 months ago* that’s a good and bad thing though… it’s easy to reference code, so it leads to tight coupling it’s easy to reference code, so let’s pull this out into a separately testable, well-documented, reusable library my main reason for ever using a monorepo is to separate out a bunch of shared libraries into real libraries, and still be able to have eg HMR permalink fedilink source parent