Performance and benchmarks? about hyperapp HOT 7 CLOSED

@leeoniya Thanks! I sent a PR to the js-repaint-perfs repo, let's hope to see it merged.

The good news are, benchmarks indicate that HyperApp is on the fast track. Careful examination of the gif seems to favor the following order for this particular test.

Inferno/HyperApp → Elm/CycleJS+Snabbdom/VueJS → morphodom

Inferno seems to do slightly better, but both Inferno and HyperApp outmatch Cycle/Vue and morphodom (but not by much). Morphodom is particularly slow though.

I think even faster than that is domvm, vidom, maybe mithril?

from hyperapp.

2017 sufficient performance is a given

certainly you don't need to be the fastest. but it helps to assure people you're not the slowest either. nothing wrong with objectivity, regardless of what year it is.

mobile performance differences are still enormous between libs. disclaimer: i've got a pretty fast horse in the game, too [1] ;)

[1] https://github.com/leeoniya/domvm

from hyperapp.

yeah, the original comment was meant to be tongue-in-cheek for this reason.

nevertheless, the benchmarks are hugely helpful (even if just to catch accidental lib perf regressions). if you can believe it, there are apps out there for which Backbone is grossly insufficient. if you've never had perf issues with Backbone, no one is prying it or jQuery from your hands, heh 😆

from hyperapp.

The docs seem to lack any mention of "blazing fast" or similar :D

Probably a positive thing. In 2017 sufficient performance is a given—I care more about ergonomics and fun.

from hyperapp.

I guess I'm just tired of new libraries claiming they're "blazing fast!!111!!!!" and focusing on that instead of other features. I mean IDK, Backbone was fast enough for me 😅

from hyperapp.

Going to close here in favor of #75.

from hyperapp.

V2's new patch algorithm (based on Superfine) is signifcantly faster than V1. Here are the benchmark results. To maximize performance, the benchmarked example app makes use of memoization to boost the rendering perf of table rows that are not affected by state changes. This technique will eventually make it into core as described in #721.

from hyperapp.