React was frontend's introduction to Big Lies. The React team themselves were talking a book they didn't fully understand (else Pete Hunt would never have been able to get on stage and say "it works like game engine!" with a straight face), and were serially unwilling to tell the full story as they knew it.
So the implausible proposition that a system that *obviously* doubled up work and didn't defend against layout thrashing would somehow be "faster" was projected and uncritically accepted.
WHY was it so uncritically accepted? JSX + weekend projects.
The promise of not having to think about how data and UI interact over time, wrapped in nice-looking forks of HTML and JS syntax, meant that the 1-10 hour project got "simpler" (assuming you ignore the hundreds of MB of NPM crap lugged in tow). Nevermind that serious teams were reliably finding themselves neck-deep in perf remediation quicksand almost as soon React got popular.
So the lie curdled: you weren't holding it right.
It was accelerated by people who sold all of this on the back of "better UX". And that's still the right yardstick: does this technology, in general, lead to better user experiences?
Obviously not. The less React (and Angular, etc.) there is in your stack, the better the UX is for *most* types of products, *most* of the time. Not a hard and fast rule, but a useful proposition to work through to understand a specific case.
@GuillaumeRossolini @sangster @slightlyoff You don't have to and what you put in there largely depends on what you want your component to be exactly. It can range from super simple ones that progressively enhances some existing markup to fully self-contained elements with its own markup, state and styles. The "range" part is the most interesting thing to me, because that means you can use as much or as little as you need.
What kind of things have you wanted to build with web components?
@hasanhaja small stuff admittedly, to get the hang of them
For example a checkbox that reuses its third state to cycle a new behavior while clicking: checked yes, checked no, undefined
@hasanhaja @GuillaumeRossolini @slightlyoff Etsy is working toward having the next version of its design toolkit built with Web Components, in large part to ensure that we can use it more easily in Mustache rendered by the server and also with our Preact apps.
Definitely proving to be more complex than we had originally expected as we sort through the nitty-gritty implementation details of really making this work for more complex components.
"...lies spread without active opposition, and that I was too quiet. I knew better; and yet."
This is hitting me hard right now.
Josh Jones
Alex Russell
Jeremy Keith
Ben
Guillaume Rossolini
Hasan Ali
Ted C. Howard
Frixy
John Allsopp
Ben Buchanan
Munawwar Firoz
Prophyt