The deleted statement was never accurate in Nx. We briefly openly explored some alternative solutions and pricing structures for self-hosted caching but this never landed as a requirement in Nx. We took on the feedback loud and clear that our initial thinking was misguided and we changed course before it landed.

We offer a broader array of free cache hosting options than Turborepo, with the OpenAPI spec being the exact equivalent of how Turborepo chooses to approach the problem, you can learn more here:

https://nx.dev/recipes/running-tasks/self-hosted-caching

For this change, I went for the most generous correction I could, but you may decide the overall section is redundant without this key incorrect point.

While I'm here, I'd suggest you run through this guide yourself again because it doesn't really make sense currently. If you run the command you have listed Nx generates package manager workspaces, no project.json files, and package.json files for each project, but then you tell people to add these things because that's "only how Turborepo does things" (not quoting but that's the inaccurate gist)...

Finally, as pointed out last time your nx.json to turbo.json comparison is very, very far from apples to apples. On the nx side you are demonstrating the configuration of a bunch of capabilities that Turborepo simply does not have and then saying "see, look, nx requires more config", which doesn't seem fair 🤷

Nx can work exactly how Turborepo works, and it can also work with optional plugins, users have complete freedom of choice. If you'd like to collaborate on further rewrites I'm totally open to that, but I thought I would keep this PR very focused on this critical correction for now.