News for hackers. Stuff that matters.
Re:Deno 1.45: Workspace and Monorepo Support by augusto-moura on Friday July 12, 2024 @08:52AM (#40945081)
How would that differ from having the 50 microservices cloned separately? Maybe you want to say that perhaps some of the microservices were not that useful and didn't need to be versioned as well? If that is the case I think you could benefit from Scalar [1]. Microsoft created it because of similar problems with size and binaries

[1]: https://github.com/microsoft/scalar

Re:Deno 1.45: Workspace and Monorepo Support by slightwinder on Friday July 12, 2024 @09:18AM (#40945291)
> How would that differ from having the 50 microservices cloned separately?

Usually, not everyone needs every single microservice, so they only checkout the handful they need, instead of the full monster. And usually one will accumulate repos over time, instead of getting them all at once. Similar, you will also only pull updates for the repo necessary for your work today, instead of getting the full update the whole company creates every day.

Re:Deno 1.45: Workspace and Monorepo Support by msoad on Friday July 12, 2024 @01:59PM (#40947893)
Sparse checkout is a new Git feature that can help with this
Re:Deno 1.45: Workspace and Monorepo Support by ethegwo on Friday July 12, 2024 @09:11AM (#40945238)
Yes, Scalar would be helpful. The problem is that not every developer needs all the code in the repository for their daily work. However, Git makes it difficult to do partial checkouts.