> 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 a bit.
Yeah, I only used Vue version 1, so I know what to stay away from. I looked at Elm for a major source of inspiration. > How to interact with third party JS libraries? We're making Karax work with emscripten and strive for good interop with Nim code, not JS code. > Why aren't components split into template/code(/style)? Because such a split only produces artificial complexity. > How do components communicate? They don't. Components should be stateless. I think we should use a different name, Karax's components are not what others call "components". > What about the tooling, i.e., how does building / bundling / browser test > running / debugging (source maps) work? Source maps are in the works and "bundling" doesn't need anything, it's generated JS code, move it to where you want. > An idea for the documentation would be to map JS artefacts like > npm/webpack/mocha/karma/selenium to possible solutions. I don't know what that means. > 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 Would it help to rename it to `jsstring`?
