The broken promise of Web Components

Re:The broken promise of Web Components by danabramov on Thursday March 16, 2017 @11:20AM (#13885719)

I found these things hard:

* Inconsistencies or duplicated code between initial render and updates.

* Having to write code for N^2 transitions between N valid states instead of N valid states themselves.

* Harder to ensure DOM operation order across different parts of the codebase doesn’t produce jank.

Sure, this is all possible to solve, but in my experience I just ended up with a crappy version of React.

[ Parent | on HN ]

Re:The broken promise of Web Components by just2n on Thursday March 16, 2017 @07:12PM (#13889987)

Seconded on all counts. We also ended up independently implementing a really simplistic and in many ways broken version of React for these reasons and many others.

[ Parent | on HN ]