4 ms·
Speaking of "dreaded diffing". It's now fashionable to bash React and VDOM and diffing, but... vdom libs are at the forefront of performance these days: https:/
by illiarian 4y ago
Speaking of "dreaded diffing". It's now fashionable to bash React and VDOM and diffing, but... vdom libs are at the forefront of performance these days: https://twitter.com/RyanCarniato/status/1636120238638137344?s=20 https://twitter.com/RyanCarniato/status/1636120238638137344?...
You need either granular reactivity or diffing (or perhaps both), or else your framework's performance will easily be trash
- eviks 4y agoit seems that it's the manually manipulated ones that are at the forefront... > I need to look closer. It does appear that the Millions implementation will get flagged as manual manipulation. So that might get changed to one a bit slower. I can't imagine anyone writing this code
- illiarian 4y agoThere's also ivi and dioxus
- localvoid 4y agoThere was a bug in ivi 2.0.0 with `shouldComponentUpdate` optimization, it was completely ignored. This benchmark submission rerenders and diffs everything on each change, all other `f(state) => UI` libraries in this benchmark are implemented with `shouldComponentUpdate` optimization. Also, unlike majority of libraries on the left side of the table, ivi doesn't use any type of event delegation(implicit or explicit) to get better results, just plain old `addEventListener()` is used internally to attach event listeners.
- danielheath 4y agoHonestly I was expecting preact to fare much worse given what you wrote. Those numbers aren’t _the best_, but given the improvement in TTI from only needing 3kb of framework that seems like a pretty good tradeoff.