Add performance suite

I’d like to propose the additon of a basic performance suite.

While micro-performance is not my primary concern, having the ability to benchmark branches against each other could be useful when making changes or optimizations, to ensure performance doesn’t degrade going forward.

I’d also be curious to include a competitive benchmark against at least one of the competing frameworks - likely the best way to do that, would be a contribution to js-framework-benchmark. I’m particularly interested in learning whether frameworks such as hyperHTML are really substantially faster because they avoid a virtual DOM intermediary. (I suspect the difference isn’t at all watershed, and/or possibly using VDOM is even faster, on account of it being so much simpler overall.)

(Perhaps js-framework-benchmark could also provide the building blocks for a benchmark suite in-project?)

If you’d like me to contribute, let me know if you have a benchmark framework preference.

[jorgebucaran]

I don’t want to add a performance suite, but instead, use @krausest’s benchmarks. I’ll add Picodom there later as I am currently rewriting the diff algorithm. The diffing/patching will follow https://github.com/hyperapp/hyperapp/issues/499#issuecomment-357557785.

Sidenote: I may eventually change the name of the library to avoid the name collision issue evident in the aforementioned benchmarks. I will definitely create a separate issue for that when the time is right.

[krausest]

@JorgeBucaran I like hyperapp and I like keyed frameworks and this is the result. (Sorry for spamming picodom)