monorepo.tools VS nx-dotnet

I'm surprised this isn't getting any attention. Reading the docs, sounds very promising, thanks for creating this! I see Nx, Turbo and Moon being mentioned in passing in [Alternatives & pitfalls](https://onerepo.tools/concepts/why-onerepo/#alternatives--pi...), but a more in-depth comparison would be interesting. At least something that could be a column in the table at the bottom of [monorepo.tools](https://monorepo.tools/#tools-review).

> I don't think anyone coming from a multi-repo world really understands the full implications of a monorepo until they've worked in a large scale one

That's entirely fair. My sole experience is the one black-sheep monorepo at my own relatively-recently joined company, which is nowhere even close to approaching true large scale.

Genuine question, though - what _are_ the advantages, as you see them (you didn't explicitly say as much, but I'm reading between the lines that you _can_ see some)? Every positive claim I've seen (primarily at https://monorepo.tools/, but also elsewhere) feels either flimsy, or outright false:

* "No overhead to create new projects - Use the existing CI setup" - I'm pretty confident that the amount of DX tooling work to make it super-smooth to create a new project is _dwarfed_ by the amount of work to make monorepos...work...

* "Atomic commits across projects // One version of everything" - this is...actively bad? If I make a change to my library, I also have to change every consumer of it (or, worse, synchronize with them to make their changes at the same time before I can merge)? Whereas, in a polyrepo situation, I can publish the new version of my library, and decoupled consumers can update their consumption when they want to

* "Developer mobility - Get a consistent way of building and testing applications" - it's perfectly easy to have a consistent experience across polyrepos, and or to have an inconsistent one in a monorepo. In fairness I will concede that a monorepo makes a consistent experience more _likely_, but that's a weak advantage at best. Monorepos _do_ make it significantly harder to _deliberately_ use different languages in different services, though, which is a perfectly cromulent thing to permit.

The section on what monorepo tools should provide is useful if you are planning to set up an enterprise-level monorepo.

The next step would be to familiarize yourself with the codebase. Most of the repositories use monorepos for organizing and managing their code. A rule of the thumb here would be to make yourself familiar with what component lies in which place. It is next to impossible to understand the entire codebase at once. For starters, you can:

Monorepos are a great concept, especially in environments like Node.js which encourage having many small packages.

You might want to use monorepo tooling like NX, Lerna, or Turborepo to guide you. https://monorepo.tools/ has a list of tools.

This explains it really well: https://monorepo.tools/

Have a look here to get some good context around monorepo tooling and if it’s something you actually need and want to do - https://monorepo.tools Some of the monorepo tooling can be a steep learning curve so you want to really think about the problem you are trying to solve and whether the effort will be worth it

I worked full stack with .net and angular for a year. I would say that is you think too OOP, you might try to do things that typescript doesn't do well. Like extending one class with multiple base clases. I've been working with Nestjs for one year or so in a personal project and I think it's amazing. You can do simple things like MVC and rest apis with little efforts. You can also work with more complex patterns like DDD and event sourcing pretty much out of the box. Because it is also JavaScript and node you can use a plethora of packages that solve your problems similarly as .net like Automapper, typeorm/mikroorm (entity framework like). In addition to a ton of open source projects that are using nestjs. Check https://github.com/nestjs/awesome-nestjs so you can explore how to get started. I would recommend you to use NX.dev to work your mono repo, it is super powerful and easy to maintain a full node mono repo. And it even has a plug in to add c# .net core projects as well https://github.com/nx-dotnet/nx-dotnet. So you can still leverage on the same tech you already know for more complex things like Identity server.

This is why DX is so important if you're going to go down the monorepo path. Angular has stuff like Nx (https://nx.dev/using-nx/caching) which helps a ton. I'm not really familiar with any .NET focused monorepo tooling. It looks like there is a .NET plugin for Nx (https://github.com/nx-dotnet/nx-dotnet) but I haven't used it so no clue how well it works..