Indeed, great idea! Did you had a look at Vue for inspiration? Many people consider it the next big thing after React, and in terms of performance it has already [raised the bar](https://vuejs.org/v2/guide/comparison.html#Performance-Profiles) a bit.
But performance is typically not the most important aspect for choosing a JS framework. Probably karax would benefit the most by making it more accessible to JS users. Some random questions (not necessarily to be answered here, just points for documentation). * How to interact with third party JS libraries? (A general question that is most likely answered in the JS backend documentation itself; just to point out that it is one of the first questions that come to mind, and linking it from karax would be good.) * How does state handling work. In a Vue/React component, I know pretty much were to look for state, in the examples I find it very hard to see. * Why aren't components split into template/code(/style)? * How do components communicate? * What about the tooling, i.e., how does building / bundling / browser test running / debugging (source maps) work? An idea for the documentation would be to map JS artefacts like npm/webpack/mocha/karma/selenium to possible solutions. * By the way, my first thought when looking at the code was: All cstring here, I'm scared -- wait, it's not even compiling to C? I think I get now why it has to be like that, but getting rid of that c could definitely reduce the scare factor for newbies .
