What's Changed
Upgrading git-cliff init. by @dessalines in #1387
Adding legal / privacy policy info. by @dessalines in #1382
Bump deps + Update baselines profiles by @MV-GH in #1389
Fix sizing by ...
Those factors lead to that we do a lot less recompositions now. Which means that that each frame we do less calculations, “keep the same UI element as before”, it is smarter at about detecting elements that stayed the same and should not be recalculated. So each frame is cheaper and it can do thus more per second
In 0.0.60 I have updated the baseline profiles (It ships the app with AOT bindings, instead of which you would get after a week from release on the playstore)
I also recommend list/small card view, if you prefer the feed to not jump due to images loading in. At some point i’ll refactor some infra so that I can Image and post preload feature out. So that it should be able to instantly load those images. But that is quite deep in the backlog.
No but my guess is they fixed some bugs that caused it to ? Or fixed the issue seperately ? Anyways i don’t think it is addressed in github release notes
Thank you @dessalines@lemmy.ml for the update.
I noticed one thing, scrolling has been improved drastically and it has become very smooth.
What was updated that made it buttery smooth?
The biggest performance changes should be from 0.0.56
Due to a compound of factors:
Those factors lead to that we do a lot less recompositions now. Which means that that each frame we do less calculations, “keep the same UI element as before”, it is smarter at about detecting elements that stayed the same and should not be recalculated. So each frame is cheaper and it can do thus more per second
In 0.0.60 I have updated the baseline profiles (It ships the app with AOT bindings, instead of which you would get after a week from release on the playstore)
Google does some amazing work, it just takes them a long time. Once this patch lands we should see more optimizations https://issuetracker.google.com/issues/241154852
I also recommend list/small card view, if you prefer the feed to not jump due to images loading in. At some point i’ll refactor some infra so that I can Image and post preload feature out. So that it should be able to instantly load those images. But that is quite deep in the backlog.
Absolutely appreciate all these details. Thank you so much for the detailed reply. Love it.
Not dessalines but i think it was .57 or .59
Would you know what happened that made it smooth?
It was a complaint I had about jerboa.
No but my guess is they fixed some bugs that caused it to ? Or fixed the issue seperately ? Anyways i don’t think it is addressed in github release notes