upvote
> People don't need components.

The idea that people don't want some sort of improved modularity, encapsulation, reusability, interop etc I think is wrong.

We can argue about whether components as proposed was the right solution, but are you arguing that templates, custom elements and modules have no utility?

Templating, for example, has been implemented in one form or another countless times - the idea that people don't need that seems odd.

Same goes for a js module system, same goes for hiding markup soup behind a custom element.

reply
That completely misses the point. You are mistaking your preference for some objective, though unmeasured, benefit.

I could understand an argument from ignorance fallacy wherein your preference is superior to every other alternative because any alternative is unknown to you. But instead, you are saying there is only way one of doing things, components/modularity/templates, and this is the best of that one way's variations, which is just a straw man.

You really aren't limited to doing this work the React way, or any framework way. If you want to continue doing it the React way then just continue to use React, which continues to evolve its own flavor.

reply
> The idea that people don't want some sort of improved modularity, encapsulation, reusability, interop etc I think is wrong.

And web components are an extremely shitty half-baked near-solution to any of those.

reply
Still not sure what you are attacking - is it just custom-elements or does that include js modules etc?
reply