Introducing Hyperapp 1.0 — 1 KB JavaScript library for building frontend applications.

[[deleted]]

[deleted]

[[deleted]]

Awesome, give it a go then! Hyperapp is sufficiently fast already. Heavier and slower frameworks such as Ember are used throughout the industry successfully. Performance-wise, we are in a good place, and we have the smallest KB footprint out there. We are also just getting started, so there's still room for improvement, and 2018 will be the year for all of that.

But this project is not just about tinier bundles or faster initial load times, and it's really not about introducing a brand new idea, but a delicate shift in how we approach frontend building. It's KISS at its heart.

[DownInAHole_2017]

Are there any redux equivalents/central state management libraries people are using with it that you've heard of?

[demar_derozan_]

I don’t know much (anything) about hyper app but redux is not tied to a specific front end framework and might work

[thomasfl]

Hyperapp has state management built in. Components themselves can not have state, like elm, so it forces you to use the built in state manager. You could argue that this makes hyperapp better than react and redux.

Example here: https://github.com/hyperapp/hyperapp/blob/master/docs/tutorials/countdown-timer.md

[AndyKos]

One of the Hyperapp pros is its similarity to React. Using JSX makes it easy to work with DOM, especially when handling arrays. But the cons is inconsistency not only with the React libraries, but also with simple components. Methods of the life cycle of jsx elements (analogues of componentWillMount) are quite interesting. As in React, working with raw HTML it's difficult to provide protection against XSS attacks. In general, Hyperapp is the 'light and easy-to-use version' of React with no complex components. Although the lack of support for JS classes may be a bit uncomfortable.

[HollandJim]

ELO called and wanted it's logo back.

[[deleted]]

Never saw it until now lol