-
-
Notifications
You must be signed in to change notification settings - Fork 111
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
Is re-executing the render function locally a good practice? #405
Comments
differently from uhtml and lighterhtml, hyperHTML doesn't have a stack concept in core, meaning same reference object, with same ID, in two places, will simply move the same node in the last place that used such reference. However, what I see here is a replica of what uland or neverland do, meaning there's nothing inherently wrong with your pattern, but hyperHTML has its own component system which, if not used, is sleeping code with no meaning, while those other libraries are born to provide this very same patern, and likely better at that, without you ever needing to reference explicitly anything. I hope this answer helps 👋 |
Yes @WebReflection , it helps. I'll take a look into neverland then. |
P.S. for an "as close as React" solution, I suggest checking kaboobie out too 👍 |
thanks for the suggestion, but being as close to react as possible is not a requirement for me 😄 |
While using hyperhtml I found myself following this pattern:
The text was updated successfully, but these errors were encountered: