It can scale, and I'd wager that it will. There is -- or should in future be -- a far larger number of software developers than the number of components that are required to compose the functionality that everyone needs and desires, at high quality and with ever-reducing negative externalities.
That's a good thing: it'll provide more time for review, apprenticeship, mentoring and mastery of individual technical areas, and for mobility and communication between communities.
That's not to say there can't also be pure-enjoyment and hobby software projects; but those won't have the same support demands (or expectations).
Small (or solo) teams maintaining systems with massive inbound demand, significant risk during changes, and limited ability to receive community feedback feels like the less-scalable approach, to me.
That said I'm willing to concede that both approaches appear to work under different circumstances (and may be able to learn from each other).
That's a good thing: it'll provide more time for review, apprenticeship, mentoring and mastery of individual technical areas, and for mobility and communication between communities.
That's not to say there can't also be pure-enjoyment and hobby software projects; but those won't have the same support demands (or expectations).
Small (or solo) teams maintaining systems with massive inbound demand, significant risk during changes, and limited ability to receive community feedback feels like the less-scalable approach, to me.
That said I'm willing to concede that both approaches appear to work under different circumstances (and may be able to learn from each other).