> That products survive this long with React illuminates how resistant the community is to... reading and doing work in the easiest, pragmatic way possible. My

> That products survive this long with React illuminates how resistant the community is to... reading and doing work in the easiest, pragmatic way possible. My point is that you were entirely wrong. Web Components are not ready for primetime, they are half baked. If they were the easiest and most pragmatic way possible to build web applications people would do so. The only thing they are the easiest and most pragmatic for is to build a simple non-form associated component that can be used across frameworks. Like a card. > It has always been a chore in one way or another. It's actually never been a chore to make an <input> behave properly. Something that literally every component library needs to do.