Skip to content
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

hyperapp #21

Open
marcus-herrmann opened this issue Aug 16, 2018 · 1 comment
Open

hyperapp #21

marcus-herrmann opened this issue Aug 16, 2018 · 1 comment

Comments

@marcus-herrmann
Copy link
Contributor

https://hyperapp.js.org/

@SteveALee
Copy link

SteveALee commented Aug 16, 2018

My thoughts on using hyperapp are that it offers the minimal possible framework of the type that is very popular for SPAs; namely VDOM views (jsx or hyperscript) + action functions + single state store. Thus it can provide a clear way to demonstrate design issues common to other frameworks.

It does have a few unique features compared to Vue, Reacts etc (but then they are all different and that is part of the vision here). V2 is imminent and makes a few big changes.

  • Only pure functional views (access state and actions) and components (props only)
  • Stateful 'components' are possible by nesting apps
  • So called Lazy components get access to global state (a bit like React context) - bit of an anti pattern IMHO
  • Pure action functions - can be automatically bound to subsets of state tree (so called slices)
  • Absolute minimal lifecyle hooks
  • Typescript support a little immature
  • Easy to use as a global script (ie via <script> tag) without build process. But then so are react and vue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants