Hey! I can think of a number of use cases: Offline-first applications (e.g. Google Docs, where the document can be available offline, or todoist, where you might want to allow user to work with the app while user is offline) E2e encrypted apps: you need to store the keys somewhere and either derive them from password, or, store locally. E.g. WhatsApp. Dynamic caching -- if the performance in your app is extremely important, and fetching the data from the remote server is slow.

The correct answer is that behaviour is not determined. (as we should know when render happens the last time). e.g. if the render happens right before TaskA, then there is a high probability, that FuncA will be executed before.

Hey Jacob, sorry, missed your comment. yes, sure, go ahead

It might not run "The whole layout", as layout is quite complicated process which has many steps, it worth to make a separate article. What can happen: the layout of the changes code has done + recalculate all "shifting" in the elements. The simplest way to see it: Open you browser dev tools Go to Performance Tab Start recording Open a website (or make some actions on opened page) Stop recording Open "Event log" Scroll to function call which makes Layerise step. Example: Select it on a timeframe to see the calculations

translateZ(0) doesn't move your render to GPU. The whole "composite" layer can be executed on GPU by modern browsers. The reason, why translateZ(0) is usually recommended to resolve some rendering issues, is because it "moves" your elements to a separate layer in browser. You can see the layers model in your browser by opening "Layers" tab: Even though this method solves some rendering issues, many Layers might cause performance issues in your app. If you want to learn more here is an article (rus) about that: https://habr.com/en/companies/odnoklassniki/articles/313978/

Updated images in the article. By accident got them removed before publishing the article 🙈