Regarding performance: these mono-repo tools work differently and are optimised for their workload. Regarding why the hell you would do it: In a corporate set

Regarding performance: these mono-repo tools work differently and are optimised for their workload. Regarding why the hell you would do it: In a corporate setting you tend to throw all kinds of st into your repo. In my workplace that includes, network configurations, 200 MB binary tools, usernames (and who knows, passwords too probably). We do this because we want all the different things, including external dependencies and "ops stuff" to be syncronised. That would be totally insane in the open source world where you are releasing to the public -- but it seems corporations can make it work internally.