Vidom - blazingly fast alternative to React

Long time I did not write anything here, but today is just Friday, so you can throw on React tell about your craft Vidom.

Short story

When only React entered the HYIP stage (beginning of 2014), the idea of ​​a virtual dom, as well as everything connected with it (diffs, patches), seemed extremely interesting to me and I decided to realize it and feel through my own implementation. I looked at the implementations that existed at that time, made several approaches, rewriting everything several times from scratch in order to achieve maximum performance. Then, gradually, components, hooks, contexts, server rendering, es2015, etc. appeared. Then I looked at the fact that people in React were in pain when used, and one of the most popular problems was the performance of server rendering and the lack of support for fragments (this task has already been in the tracker for almost two years!). Rolling up my sleeves, I added support for the fragments. And the ssr performance in Vidom was originally incorporated into it, the result of the benchmark can be seen below.

The result was:

How does Vidom look like React?

• virtual dom under the hood
• jsx
• the ability to create your own high-level components, both on the basis of classes and on the basis of functions
• lifecycle hooks in class-based components
• easy subscription to DOM events
• context api
• isomorphism, ssr, the ability to reuse markup that came from the server
• plugin for chrome developer tools

How Vidom differs from React

• speed, speed and speed again
• target platform only browsers
• support of fragments, which allows, for example, from one component to return several others (without unnecessary and, sometimes, interfering with DOM wrappers) or to manipulate several nodes, including DOM, as one.
• there is no need to set the key in simple cases when using arrays
• library size (approximately 8Kb after gzip)
• missing propTypes
• absent, and this is the main disadvantage, thousands of related libraries, such as, react-router, react-redux, etc. :)

Benchmarks

Repaint rate challenge
UI bench
Server-side rendering (node ​​v4.4.3, NODE_ENV = production):

Project on github: vidom

Ready to answer your questions, as well as see the issue and pull request on github;)