You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was and still am very intrigued by this repository.
I was wondering what you have given to such thoughts such as it’s potential future, it’s roadmap (ish?), and maybe anything you can speak to about usage? Like react compatibility.
I think given it’s size it wouldn’t be unreasonable to see this as a Preact alternative?
Also wondering if your looking to take on contributions
The text was updated successfully, but these errors were encountered:
This repo is actually 2 projects. The first, babel-plugin-transform-jsx2, is actually a complete transform ready to be used to create "static template" JSX trees. However, there are currently no runtime libraries that can handle a static template.
That's the goal of the second project, jsx2 (confusingly named, I know). The jsx2 renderer is meant to be a prototype to demonstrate the performance gains due to static template trees. I predict faster JS parsing (the output code is smaller and much easier to parse), faster initial renders (we no longer need to call React.createElement which is polymorphic and very slow), and faster rerendering (static templates eliminate GC pressure).
So the goal isn't really React compatibility, or even a replacement Preact implementation. The goal is to get these established projects to use a much better JSX format.
Also wondering if your looking to take on contributions
I'm always happy for help, and that would probably inspire me to continue working on it. Right now, the "normal" JSX rendering is done, and we're able to actually render into DOM. All that's left is implementing the static template JSX rendering (which should be easy), and implementing/optimizing the rerendering when using static templates.
Hello!
I was and still am very intrigued by this repository.
I was wondering what you have given to such thoughts such as it’s potential future, it’s roadmap (ish?), and maybe anything you can speak to about usage? Like react compatibility.
I think given it’s size it wouldn’t be unreasonable to see this as a Preact alternative?
Also wondering if your looking to take on contributions
The text was updated successfully, but these errors were encountered: