@baldur Fantastic post. My only minor quibble is that...

@baldur Fantastic post. My only minor quibble is that I do think the React team has kept innovating – concurrent rendering and RSCs come to mind. Although I'm not convinced the first is a great idea (https://nolanlawson.com/2022/10/22/style-performance-and-concurrent-rendering/) and the second seems to be heavily dividing the React community, I have to give them credit for having the guts to try new stuff even though they're the clear market leader.

Like 9 October at 17:10 | Wall-to-wall | Open on toot.cafe

3 comments

Nolan Lawson

@baldur BTW I never understood the whole Liskov substitution thing until this post. It's not just a problem for built-ins, but also web component libraries that allow subclassing. Any change to the superclass is effectively a breaking change unless the subclass automatically gets the new behavior somehow (e.g. super.connectedCallback).

9 October at 17:20 | Open on toot.cafe

Alex Russell

@nolan @baldur This was always true! We wanted to add traits or some other factoring mechanism to allow for decomposition, but TC39 could barely do intrinsic subclassing w/ `class` syntax in a ~timely way.

9 October at 17:32 | Open on toot.cafe

Alex Russell

@nolan @baldur DOM is crying out for decomposition to mixins/traits, and we hoped to do it. But browser vendors whatabouting without actually investigating developer problems (and failing to implement what they stopped the presses to relitigate) dragged everything out.

9 October at 17:34 | Open on toot.cafe