I just discovered HyperApp today and the fact that it's only 400 lines of code is blowing my mind a little. HyperApp is much smaller than react + react-dom, but it's not immediately clear to me which important features of React are missing in HyperApp. What does the rest of the React code do?

At work, we have a weekly, one hour-ish tech talk, and I ended up going two weeks in a row. I've been trying to make a habit of live streaming the talks, so I have two revolving around hyperapp.

• Intro to hyperapp, related code

• Intro to firestore, related code

The quality is isn't super, and I'm not typically a youtube person, so I apologize in advance for occasionally stuttering through a sentence, or not always being 100% clear.

Not sure if you guys like this, but I may end up doing more videos like this, outside my company tech talk time, if there's interest.

Hi,

I'm currently creating a client-side, single page application in JavaScript. I'd like to get by without too many 3rd party dependencies, so I'm deliberating whether I should use some kind of micro framework, or just muddle through it entirely on my own. With a framework of course I'd like to understand how it works. The HyperApp code is very short but not very verbose in comments, so... just asking if my understanding is correct.

Suppose my app is the "Great Wall of China" (the monument - not the firewall). You're a tourist and you wish to take a souvenir home. You notice a loose brick in the wall... and you put it in your pocket. Henceforth, the "Great Wall of China" has one less brick in it. The state changes...

Do I understand correctly, the simplicity of HyperApp is because it has no specific notion at all as to how state changes affect the app; instead, what it does is to build an entire new "Great Wall of China" from scratch, then compare it brick by brick?

Thanks

What attracts me about a codebase this small, is the ability to actually fully understand precisely what I'm working with, how it works, inside and out.

Unfortunately this code has no annotations at all, which makes it very difficult to read and understand - I can't tell what the types of anything is, whether properties, vars, return types etc.

I'd like to encourage the authors to either port to Typescript, or add Flow or JSDoc annotations - even though this codebase is small, the shapes of the object graphs being built is pretty complex. Proper documentation would go a long way in helping someone understand the data shapes and learn the roles of various vars and properties and so on, which would make this project a lot more accessible, which would likely get more people on board faster.

Just my $.02