update ivi and switch template to @ivi/htm #1778
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
leeoniya
changed the title
|
Results will appear in the chrome 131 run (hopefully soon). |
|
From 1.11 to 1.11 is acceptable I'd say. Results are up. |
|
heh, the compiled bundle is identical, so that's great news...for the benchmark itself 😅 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
this switches ivi to use its @ivi/htm template syntax, which i think makes this awesome framework feel a lot less esoteric. the compiled bundle is identical.
i've kept the
.textContentprop optimizations in place, but will do a follow-up PR to see how much omitting these affects performance. (@localvoid says memory usage would go up slightly)