I fortunately quit animating height quite a long time ago in favor of similar transform techniques, but… wow, still crazy to learn the magnitude of this common operation.
Don't animate height
21–30 of 276 posts
Re: Don't animate height
#22Re: Don't animate height
#23The post is also riddled with all kinds of misunderstandings, as well. For example, the authoritative language used to describe the differences between layout/painting/compositing is just simply untrue generally speaking (though it might be w.r.t. Electron/Chromium). The W3C does not care how you implement your rendering engine, and even bringing up the spec betrays a misunderstanding of how these things work.
In typical fashion, we see yet another grandiose blog post about fixing a "perf issue" for your hipster new startup that is essentially notepad.exe. Who funds this shit?
Re: Don't animate height
#24Great writeup. With LLMs doing an increasing amount of the coding now, it would be great for the browser or development environment to have built-in validations that enforce good performance. The coding agent (or human) would get direct, immediate feedback at development time that there's a performance threshold violation, at development time.
Re: Don't animate height
#25"What is Granola spending those cycles on? It's an Electron app" Yup. Matches my experience with pretty much every Electron app. Great that the dev tracked it down, but every Electron app is a waste of...electrons
You know what else was a waste of electrons? Your comment, and my reply.
Re: Don't animate height
#26So, after all the optimization, they're using 6% of the CPU to display what amounts to a tiny animated GIF that 1990s PCs would have no problem with. But it's vector graphics! , you might say. Yeah, like Flash, which ran fine on Pentium II, with plenty CPU cycles to spare. Pardon me, and I don't say it lightly, but... WTF?!
Re: Don't animate height
#27So, after all the optimization, they're using 6% of the CPU to display what amounts to a tiny animated GIF that 1990s PCs would have no problem with. But it's vector graphics! , you might say. Yeah, like Flash, which ran fine on Pentium II, with plenty CPU cycles to spare. Pardon me, and I don't say it lightly, but... WTF?!
Re: Don't animate height
#28"What is Granola spending those cycles on? It's an Electron app" Yup. Matches my experience with pretty much every Electron app. Great that the dev tracked it down, but every Electron app is a waste of...electrons
Might be worth getting off of that high horse. You are not being very smart by saying 'akctually electron bad'. You know what else was a waste of electrons? Your comment, and my reply.
Re: Don't animate height
#29Wondering what the performance of a simple animated gif would be, instead of the composite layer transformations.
If the bars are not related to actual data and are purely just pre-canned animation, the gif would just come with additional file size for a one time cached type of download. If the bars do need to be animated to real-time data coming in, then the gif would not be the right fit for that need.
Re: Don't animate height
#30Earlier quoted context omitted.
Might be worth getting off of that high horse. You are not being very smart by saying 'akctually electron bad'. You know what else was a waste of electrons? Your comment, and my reply.
Your reply was not necessary though. Every electron app uses more of my computer's resources than when I use the same service through the web browser.