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

Vdom awareness - fixes #19 #21

Merged
merged 1 commit into from
Jan 29, 2016
Merged

Vdom awareness - fixes #19 #21

merged 1 commit into from
Jan 29, 2016

Conversation

StephanHoyer
Copy link
Owner

…des in translations

@StephanHoyer StephanHoyer force-pushed the vdom-awareness branch 3 times, most recently from 71f4732 to 7e8e716 Compare January 29, 2016 12:06
@StephanHoyer
Copy link
Owner Author

@maranomynet what do you think?

@StephanHoyer StephanHoyer force-pushed the vdom-awareness branch 2 times, most recently from 08428cb to fec75f2 Compare January 29, 2016 12:11
@maranomynet
Copy link
Collaborator

See inline discussion in 71f4732

StephanHoyer added a commit that referenced this pull request Jan 29, 2016
@StephanHoyer StephanHoyer merged commit 2ef7fd6 into master Jan 29, 2016
@StephanHoyer StephanHoyer deleted the vdom-awareness branch January 29, 2016 13:23
@maranomynet maranomynet mentioned this pull request Jan 29, 2016
@maranomynet
Copy link
Collaborator

BTW, I updated benchmark.html in 5103c1f and it shows that with v0.4.0, the performance of replacements basically tanks. :-(
My WIP feature/array_option branch improves things a bit, but it's still an order of magnitude slower than v0.3.2.
I'm exploring options as to how to get the old performance back.

@maranomynet
Copy link
Collaborator

I'll add comments on the process in #22

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.

2 participants