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

Updated Voby to v0.14.0 #1017

Merged
merged 5 commits into from
Mar 29, 2022
Merged

Updated Voby to v0.14.0 #1017

merged 5 commits into from
Mar 29, 2022

Conversation

fabiospampinato
Copy link
Contributor

  • v0.12 had faster clearing but it left some work to do in the future potentially, now clearing may be a bit slower but there's no leftover work or risks of memory leaks, though I had to resort to some manual disposition to gain some of that performance back.
  • A fairly important bug got fixed, it just made things less efficient though, the framework still worked correctly as far as I can tell.
  • The cache behind the crucial For component is more optimized.
  • The framework is now tree shakeable, and its core is mangled.

Basically the framework should do better on memory usage and startup tests, but it may be a bit slower.

Apparently today/tomorrow Chrome 100 will be released, I hope I submitted this in time for that.

@krausest krausest merged commit a80497b into krausest:master Mar 29, 2022
@krausest
Copy link
Owner

Thanks - here are the results:

Now I'll try to move all frameworks to chrome 100!

@krausest
Copy link
Owner

JFI: Chrome 100 is somehow unexpected:
#1020

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