Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to Mithril 1.0 #10

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Migrate to Mithril 1.0 #10

wants to merge 1 commit into from

Conversation

simov
Copy link
Contributor

@simov simov commented Aug 26, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant