Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I decided to drop the benchmarks for Mithril 0.x entirely and migrate to Mithril 1.0 instead. Last time I checked the rewrite was deemed unstable, but now it seems to be pretty stable, although not officially published yet.
Another thing is that Mithril 0.x is in maintenance mode for a very long time now and performance improvements are not being added there.
The rewrite is hosted here. The updated docs are here, and more importantly the migration guide.
The initial loading of the for-each benchmark is faster than Oval. Removing, adding and refreshing the items is pretty much the same as in Oval, so good job on that.
The timers demo calls
m.redraw
inside each and every interval timeout, so at least from the end-user's point of view the code looks identical to any other framework. No more batch redraw called outside of the async callbacks. Seems to be working this time.