-
Notifications
You must be signed in to change notification settings - Fork 16
preact backend #31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Apparently preact has a layer for compatibility with react. |
It should be fairly straightforward to create a new backend as long as it has -
For libraries that have a virtual-dom already, it's the first part (purescript bindings) which is usually the largest hurdle. Preact is a drop-in replacement for React, so it should be a lot easier to create Purescript bindings for it, if they don't exist already. Once we have Purescript bindings, I would be happy to help out with any new backend projects, or even build those backends myself. |
Nerv is probably a better candidate as it's faster and is compatible first, and preact loses speed with used with compatibility layer. |
I'm going to close this, and open an umbrella issue for alternative backends. |
Closing this in favor of the umbrella issue. |
Uh oh!
There was an error while loading. Please reload this page.
All 3 of those are lighter by a wide margin, while maintaing same symantics. 200 kb bundle is no good.
The text was updated successfully, but these errors were encountered: