Keo VS inferno

Keo - Plain functions for a more functional Deku approach to creating React components, with functional goodies such as pipe, memoize, etc...

FormEvent event.target has been explicitly defined for this event type c337fdd

Added a warning when rendering links with javascript: URLs 7bc3763

I mean I don't know what your monorepo looks like, but for example infernojs (actually written with typescript) uses lerna, and lerna seems simpler than typescript references

Svelte just got a lot more interesting! Dominic who is the creator of LexicalJs and InfernoJs (which is known to be insanely fast) has joined the svelte core team and is now working at Vercel full time! Here is the announcement on Twitter!

Inferno.js uses VDOM https://github.com/infernojs/inferno and is faster than Svelte according to these benchmarks https://krausest.github.io/js-framework-benchmark/2023/table.... Sooo, VDOM can improve performance?

Inferno (~6 years old) uses a VDOM, just like React, but it completely smokes React in benchmarks

Some might argue that React’s relatively poor performance (it’s still plenty-fast for many apps) is due to Virtual DOM and prioritization of development experience, i.e., clarity over complexity. To counter the first argument - there’s React-like Inferno. For the second one - there’s Solid.

1. Inferno:

A VDOM library like Inferno uses this information to compile its JSX directly into pre-optimized node structures. Marko, and Vue hoist their static VDOM nodes outside of their components so that they don't incur the overhead of recreating them on every render.

InfernoJS