6 ms·

This is an exceptionally simple library to use in place of React. Both its performance and the development experience have been great. My company's been using

This is an exceptionally simple library to use in place of React. Both its performance and the development experience have been great. My company's been using it in production for more than a year now without any issues. Highly recommend giving it a look.

pault 8y ago
Just out of curiosity, what was your use case that you deemed this a better option than react for?
- hellcow 8y ago
  We use Hyperapp to power our most complex UIs (decision trees, onboarding sequences, etc.). We didn't need any of the existing React ecosystem for that, and by removing React, we saw several benefits: 1. Smaller library for faster page loads 2. Simpler API, docs and library made it easy to get started and understand what's happening behind the scenes as well as debug any issues we faced 3. We aren't supporting a project run by Facebook, which I personally view as a good thing given Facebook's many previous issues. Facebook's patent clause (while it no longer exists) was a factor in our original decision. I would choose Hyperapp again for my company, and I use it for personal projects as well.
  - m0meni 8y ago
    Why not Preact?
    - hellcow 8y ago
      It came down to preference. I find HyperApp's codebase simpler to read/reason about (it's a pretty straightforward single file), and I prefer its API over React/Preact's.
    - starbuzz 8y ago
      Because Preact and Hyperapp are solving slightly different problems. Hyperapp is Elm-like state management (and soon effects and subscriptions in 2.0) on top of an ultra-lightweight virtual DOM diff engine. Preact is a React 15 clone at best. Check out also https://github.com/NervJS/nerv https://github.com/NervJS/nerv for another React clone that is closer to React 16 (but still no fiber).
agumonkey 8y ago
people should really give it a book
- starbuzz 8y ago
  I guess look? :) There's a book though: https://booth.pm/ja/items/825889 https://booth.pm/ja/items/825889 (Japanese)

pault 8y ago

Just out of curiosity, what was your use case that you deemed this a better option than react for?

hellcow 8y ago
We use Hyperapp to power our most complex UIs (decision trees, onboarding sequences, etc.). We didn't need any of the existing React ecosystem for that, and by removing React, we saw several benefits: 1. Smaller library for faster page loads 2. Simpler API, docs and library made it easy to get started and understand what's happening behind the scenes as well as debug any issues we faced 3. We aren't supporting a project run by Facebook, which I personally view as a good thing given Facebook's many previous issues. Facebook's patent clause (while it no longer exists) was a factor in our original decision. I would choose Hyperapp again for my company, and I use it for personal projects as well.
- m0meni 8y ago
  Why not Preact?
  - hellcow 8y ago
    It came down to preference. I find HyperApp's codebase simpler to read/reason about (it's a pretty straightforward single file), and I prefer its API over React/Preact's.
  - starbuzz 8y ago
    Because Preact and Hyperapp are solving slightly different problems. Hyperapp is Elm-like state management (and soon effects and subscriptions in 2.0) on top of an ultra-lightweight virtual DOM diff engine. Preact is a React 15 clone at best. Check out also https://github.com/NervJS/nerv https://github.com/NervJS/nerv for another React clone that is closer to React 16 (but still no fiber).

agumonkey 8y ago

people should really give it a book

starbuzz 8y ago
I guess look? :) There's a book though: https://booth.pm/ja/items/825889 https://booth.pm/ja/items/825889 (Japanese)