It's quite impressive how many layers of oopsies there are in the React api now.
The curse of being successful as a software project: more people want more from you, but you are not allowed to actually remove cruft, because too many people depend on it.
The entire concept of mitigating un-intended re-rendering by wrapping your bad abstractions in more abstractions is not a category of problem for Svelte devs nor is it inherent to the platform like some inevitably of scale.
React is bad because its foundation is a bad abstraction (v-dom) and it’s spent over decade pilling on more leaky abstractions every year, leading to where we are now — clamoring over a mountain of footguns and indirection.
Obligatory Fireship video: https://www.youtube.com/watch?v=yl0YWA2K2B0&t=40
It's quite impressive how many layers of oopsies there are in the React api now.
The curse of being successful as a software project: more people want more from you, but you are not allowed to actually remove cruft, because too many people depend on it.
19: 193 kB -> 60.3 kB (gzip) https://bundlejs.com/?q=react%4019.2.0%2Creact%4019.2.0%2Cre...
18: 142 kB -> 45.6 kB (gzip) https://bundlejs.com/?q=react%4018.3.1%2Creact%4018.3.1%2Cre...
The entire concept of mitigating un-intended re-rendering by wrapping your bad abstractions in more abstractions is not a category of problem for Svelte devs nor is it inherent to the platform like some inevitably of scale.
React is bad because its foundation is a bad abstraction (v-dom) and it’s spent over decade pilling on more leaky abstractions every year, leading to where we are now — clamoring over a mountain of footguns and indirection.
Yes. VDOM is immediate mode. DOM is retained mode. Building immediate mode on top of retained mode is cursed.
React.memo(MyFlowNodeComponent) like this?