[ilaksh]

There doesn't need to be a practical reason for something to not be popular. Popularity and merit are not the same thing.

Web components aren't popular because they haven't become popular yet. There is a lack of sufficient network effect moving in that direction.

Once they start becoming popular, the issues with them (which are relatively minor) will be resolved quickly and improvements added.

Why are most of our cities and cars still designed with fundamentals basically the same as in the 1930s? Not because there aren't better designs. It's just momentum.

High technology is like that still even though nothing physical needs to be changed.

Humans are herd animals. And the rationalization for behavior comes after the behavior not before. We subconsciously copy what other people are doing. People use React or whatever flavor-of-the-month.

Give it a couple of years and many of the flavor-of-the-month frameworks will probably be built on top of web components.

[sbergot]

The design of cars has evolved a lot, mainly because of security regulations. Cities is another topic. They change slowly because of the required investment but in europe at least there is definitely a trend toward walkable blocks which changes a lot of urbanisation guidelines.

I agree with your first sentence: things are unpopular by default. However I disagree with your assumption: web components won't become magically popular overtime without a good reason for them to be used over all the other options. Your "flavor-of-the-month" take ignores the fact that react is now 10 years old and is boring tech. It is still one of the most widely used frontend framework.