Thanks for your reply and I totally agree that Web Components are only part of the puzzle called web development. I definitely would advise teams to use a framework, because all of the reasons mentioned by you. You don’t want (and need) to invent that yourself.

What I mean is that many tech companies are successful, because of the autonomy they give to the development teams. In order to thrive, teams have to feel comfortable with a certain tech stack. Therefore they need to be able to make their own choices. The other side of the coin is that it will become difficult to exchange reusable components and knowledge between teams. I think that this problem can be solved when companies provide development teams with framework agnostic components libraries. This will serve as an addition to the preferred stack.

I would advice companies to provide development teams with a certain amount of autonomy, but also provide a way in which components can be exchanged in a simple and efficient way (i.e. framework agnostic components libraries).