Live data from Hacker News

Hyperapp – A tiny framework for building web interfaces

hyperapp.dev

11–20 of 198 posts

Re: Hyperapp – A tiny framework for building web interfaces

#12

I have tried Hyperapp some time ago. It's usable for small apps, but the lack of ecosystem makes it unfit for anything larger -- as is usual for all niché JS frameworks. Funnily, the "ecosystem" page contains just Lorem Ipsum ( https://hyperapp.dev/ecosystem ) and the Awesome Hyperapp section for V2 is almost empty ( https://github.com/jorgebucaran/awesome-hyperapp )

It's been like that for months - seems like the project is not seeing the activity they expected for v2.

Also server-side routing is broken and that link will not work.

Re: Hyperapp – A tiny framework for building web interfaces

#13
I've used this for building the browser extensions for my app [1].

It is simple, easy to understand and easy to reason with. However, I would recommend this only for small apps. As soon as your app's features/complexity increases, you end up writing a lot of biolerplate code that libraries like Vue or Preact already handle you for.

[1] https://www.emailthis.me

Re: Hyperapp – A tiny framework for building web interfaces

#17

When last I checked, Hyperapp was basically the elm architecture implemented in JS, a gateway drug.

I had the impression it was the other way around.

People starting with Elm, love the idea, but not the ecosystem, and come back to JS in the end.

That's how Redux was created.

Re: Hyperapp – A tiny framework for building web interfaces

#18

I've used this for building the browser extensions for my app [1]. It is simple, easy to understand and easy to reason with. However, I would recommend this only for small apps. As soon as your app's features/complexity increases, you end up writing a lot of biolerplate code that libraries like Vue or Preact already handle you for. [1] https://www.emailthis.me

Your open source browser extension framework was really helpful to me a few years ago!

Re: Hyperapp – A tiny framework for building web interfaces

#19

I love it, but I actually stuck with version 1, which was way more intuitive for me. Just a side note, I'm not fulltime front-end, so keeping up with modern frameworks is out of my capacity. It's great for smart components to my standard multi-paged systems, but I used it even for small PWA applications.

I resisted the change to v2 for a long time. In the end I found that v2's state management is much better, so it might be worth a look for that alone.
Post reply on HN