If you care, you should read about how Google makes sure this doesn't happen.
> By putting our revision history in the cloud we provide engineers with complete access to all the source, and yet almost no time is spent checking out code.
http://google-engtools.blogspot.com/2011/06/build-in-cloud-a...
http://google-engtools.blogspot.com/2011/08/build-in-cloud-h...
That said, I find your note a bit amusing. I'd have agreed a decade ago, but nowadays, 50 MB should take effectively zero time for you to both download and apply. It's worth revisiting things like this as LANs and the internet get faster; I think the speed comment is a bit outdated now.
I agree that it should take effectively zero time for me to download and apply 50MB of updates, but poor quality internet is still pretty easy to find (working with plane wifi) -- maybe my coffee shops have worse internet than yours!
Go on vacation for two weeks? You get to go on another vacation while you wait for your monorepo to update. Similarly, good luck ever trying to work from a coffee shop -- at the very least you probably have 50mb of updates because everyone in the company is committing code all the time.