starbuzz

Duplicate of https://news.ycombinator.com/item?id=17132823

^ This

The irony is you are the extremist for thinking HN is full of extremists! :)

Also, library size !== mediocrity at all. No one builds an unreasonably large framework on purpose either.

> So far, the Infinite monkey theorem is just giving us an infinite number of javascript frameworks, and no Shakespeare

Not even funny IMO. This is the kind of toxic comment that don't motivate progress in this community.

Hyperapp is not optimized to be the fastest framework at the expense of worse developer experience. Having said that, we're definitely working on improving our runtime performance (see https://github.com/hyperapp/hyperapp/issues/499). So much to do!

I want to point out that while these benchmarks are very useful to detect underlying, potentially serious runtime and memory performance issues in your algorithm/framework, the implicit idea that even the slowest framework according to this list (e.g. choo) is a poor choice or inadequate for frontend development is ridiculous (the js-framework-bench creates > 80,000 nodes).

Please don't do that to your users, regardless of the framework you are using. Even the most complex user interface will have < 10,000 nodes. Tables/grids may get you there faster, however.

Still, in the case of Hyperapp we're talking about 100 to 200 milliseconds slower in the worst test (i.e., partial update) for a worst-case scenario.

I meant the benchmark is using an older version of Hyperapp.

https://github.com/krausest/js-framework-benchmark/tree/mast...

The js-framework-benchmarks is very much maintained and actively developed. It's our go-to benchmark when fine-tuning for a new release.

In addition to that, the latest code on master (still unpublished) includes some notable improvements:

https://github.com/hyperapp/hyperapp/pull/663

If all goes according to plan, it will look even more like Elm in the next major release (2.0).

Elm is for anyone. I love Elm.

"for the rest of us" is a common English language idiom/phrase.

https://english.stackexchange.com/questions/41687/meaning-of...

I know the idiom mostly from For Dummies' books. I'm implying that Elm, while great, is not as user-friendly, intuitive or easy to use as Hyperapp.

I'm saying that Hyperapp is deeply inspired by Elm, but also designed with extreme devotion to details, minimalism, and simplicity.

Hyperapp and Web Components is a great combo, especially because they can help with the problem of maintaining local component state, not a feature of Hyperapp.

Yes. Not IE8, though.

Hyperapp will be a lot more Elm-like in a future release, see this too: https://github.com/hyperapp/hyperapp/issues/672

HyperTerminal

I replied to another similar comment but the TL;DR is that both are solving different things. Preact is a React 15 clone.

Hyperapp is basically Elm in JavaScript.

This is a crucial aspect of Hyperapp that often goes unnoticed because simply no one in their sane judgment expects it.

Surely there are many more ways.

Oh, Mithril! All folk desired it. This one is great too.

This is an old benchmark, we're in the same ballpark as React now. Hyperapp is also not just a virtual DOM, but also a state management "all-in-one" kind of thing.

Hyperapp has a great API, it's easy to use and it's 1 kB.

Some of those results refer to HyperTerminal, the Electron-based terminal app. Other results refer to Hyperapp-like libraries (not Hyperapp). The most recent submission related to Hyperapp was 8 months ago and Hyperapp has come a long way since then.

Here is another angle to this: go into React type of submissions and ask them to stop spamming HN with that?

https://hn.algolia.com/?query=react&sort=byPopularity&prefix...

Hyperapp is based on virtual DOM and yes, I guess you could say it's inspired by Hyperscript in the same way as all virtual DOM based libraries or frameworks.

Hyperapp and Web Components are a great pair.

Hyperapp is Elm for the rest of us. I wouldn't compare it to React as they are solving slightly different problems. Hyperapp's state management is built-into the framework. In this way, Hyperapp is a tad more "high-level" (abstract) than React.

I guess look? :)

There's a book though: https://booth.pm/ja/items/825889 (Japanese)

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).

Maybe there's simply nothing else to say.

That, no one can beat.