News for hackers. Stuff that matters.
Re:Show HN: HyperApp – 1k JavaScript framework for building ... by pault on Tuesday May 22, 2018 @01:55PM (#17127976)
Just out of curiosity, what was your use case that you deemed this a better option than react for?
Re:Show HN: HyperApp – 1k JavaScript framework for building ... by hellcow on Tuesday May 22, 2018 @02:53PM (#17128460)
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.

Re:Show HN: HyperApp – 1k JavaScript framework for building ... by m0meni on Tuesday May 22, 2018 @03:26PM (#17128696)
Why not Preact?
Re:Show HN: HyperApp – 1k JavaScript framework for building ... by hellcow on Tuesday May 22, 2018 @03:49PM (#17128850)
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.
Re:Show HN: HyperApp – 1k JavaScript framework for building ... by starbuzz on Tuesday May 22, 2018 @07:16PM (#17130263)
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 for another React clone that is closer to React 16 (but still no fiber).