5 ms·

> Nevertheless, one of the things that React 17 changes is how event delegation works. This is one of the reasons why I only ever touch React or similar framew

> Nevertheless, one of the things that React 17 changes is how event delegation works. This is one of the reasons why I only ever touch React or similar frameworks when forced to do so at gunpoint. If a library author is on their 17th major version and is still deciding how core stuff like this works, I have no confidence they're ever going to settle on a long-term solution. Just give me the standardised web APIs thanks, that's a perfectly suitable framework. At least these converge towards consistency and have been (and will remain) stable for decades. The last thing I want to spend my time on is constantly chasing API breakages.

filoeleven 4y ago
> If a library author is on their 17th major version and is still deciding how core stuff like this works… Did you follow the link to understand what the change is, and why they made it? [link] This isn’t some sweeping rewrite of an entire subsystem for the fourth time (I’m looking at you, Angular); it’s just changing React’s synthetic events to be attached to the react tree’s root node in the DOM instead of directly on the document. They have always been on the document until now. So there is no “still deciding” flip-floppery here, there was a single decision made to better support developers by making one low-impact change. How low-impact? > We’ve only had to change fewer than twenty components out of 100,000+ in the Facebook product code to work with these changes…[link] React is very good about semantic versioning. This change, small as it is, is a breaking change for a very small number of users. And that’s why it gets a new major version number. https://reactjs.org/blog/2020/10/20/react-v17.html#changes-to-event-delegation https://reactjs.org/blog/2020/10/20/react-v17.html#changes-t...
Kaze404 4y ago
The web has existed for at least 22 years and we still leave such implementation of "standardised" web APIs entirely to the vendor's discretion. I wouldn't call that converging towards consistency or stable.
- wruza 4y ago
  So web can’t converge and popular frameworks can’t converge. What’s the answer then, or what sense that makes?
  - Kaze404 4y ago
    I never claimed to know. My point is that Web APIs aren't the answer, like the person I replied to said.

filoeleven 4y ago

> If a library author is on their 17th major version and is still deciding how core stuff like this works… Did you follow the link to understand what the change is, and why they made it? [link] This isn’t some sweeping rewrite of an entire subsystem for the fourth time (I’m looking at you, Angular); it’s just changing React’s synthetic events to be attached to the react tree’s root node in the DOM instead of directly on the document. They have always been on the document until now. So there is no “still deciding” flip-floppery here, there was a single decision made to better support developers by making one low-impact change. How low-impact? > We’ve only had to change fewer than twenty components out of 100,000+ in the Facebook product code to work with these changes…[link] React is very good about semantic versioning. This change, small as it is, is a breaking change for a very small number of users. And that’s why it gets a new major version number. https://reactjs.org/blog/2020/10/20/react-v17.html#changes-to-event-delegation https://reactjs.org/blog/2020/10/20/react-v17.html#changes-t...

Kaze404 4y ago

The web has existed for at least 22 years and we still leave such implementation of "standardised" web APIs entirely to the vendor's discretion. I wouldn't call that converging towards consistency or stable.

wruza 4y ago
So web can’t converge and popular frameworks can’t converge. What’s the answer then, or what sense that makes?
- Kaze404 4y ago
  I never claimed to know. My point is that Web APIs aren't the answer, like the person I replied to said.