A highly specialized web application builder or an endless copy-paste of the same functionality?

Question

Web development

Many web applications are similar, at least in some narrow areas. For example, accounting for employees in a company or accounting for students in an educational institution, or accounting for products in a warehouse. And, theoretically, it would be possible to make a web application constructor, in which each institution would customize the interface and database for itself, and the main functionality would be general, programmed 1 time. And if you look at the current state of affairs without a constructor, then for all similar companies they write applications that are the same in terms of functionality, even if different programmers at different times. Or they could not reinvent the wheel 10 times, but use a product already invented by someone - a constructor, where they could assemble the application themselves, without copying the code written by someone earlier and without inventing bicycles. For example, a programmer received an order for a web application. And he understands that a similar application is needed in another area, even if it will be needed in a few years. Why copy-paste the code in the future from this application, if you can make a constructor, and then the customer configures the application as he wants? And immediately a niche for a new product (designer) automatically appears. Isn't it?

Answer 1

That's why everyone has been using frameworks and libraries for a long time.

Answer 2

Such a constructor is called 1C.