When a programmer thinks to herself I see the author is in the "they is not a singular pronoun" camp, which means we cannot be friends. Anyway I don't know ho

When a programmer thinks to herself I see the author is in the "they is not a singular pronoun" camp, which means we cannot be friends. Anyway I don't know how it is in other parts of the stack, but based on my experiences on the front-end, to build a large-scale project you're going to need a: - Router - Way to manage forms & validation - Way to communicate with the backend - Set of tools for testing - Set of commonly used components - that includes layout - 118n support - Convention where to put certain files and how to name them - Store So it would make sense to have all this in one coherent framework. That being said not all projects are large-scale projects. Normally you'll only need a subset of the mentioned. Bottom line is it's a question of scale.