On top of that this report exists for a reason, and has nothing to do with React or VDOM
Web Components Community Group: 2022 Spec/API status
This is required.
(w3c.github.io)
On top of that this report exists for a reason, and has nothing to do with React or VDOM
This is required.
(w3c.github.io)
This is what is so frustrating in the web components discourse.
Devs and web framework authors: here's a laundry list of reasons why we use what we use. This list contains a multitude of things: from convenience to purely technical considerations.
Web components: straw man, skill issue, invented problems...
...
Web components: BTW have you tried this alternative that ships with a compiler and custom syntax more ad-hoc than JSX and rules more weird than hooks?
@GuillaumeRossolini @slightlyoff
To the point that our assumptions about perf bottlenecks end up being wrong and appear in a different place from what we originally assumed
2/2
@GuillaumeRossolini @slightlyoff
What's frustrating is that sometimes the bad performance isn't really the result that of a framework used, or true incompetence.
We're now investigating and refactoring an app of ours. There's nothing really too odious... but a death by a thousand cuts: features brought in under impossible deadlines, invalid device assumptions, original architecture not evolving for new requirements etc.
1/