4 ms·
You have to have some ideas of what the state was before the change, and what changes need to be done to transfer states. In complex UIs, writing custom update
by pitaj 8y ago
You have to have some ideas of what the state was before the change, and what changes need to be done to transfer states. In complex UIs, writing custom update logic for every change results in an unmaintainable mess and a large payload to the client.
- baybal2 8y agoYes, but proper, technically superior ways for "data binding" and templating were around since IE6 era, just back then people were not concerned much with doing things properly with javascript as the universal presumption was "if it uses JS it will be slow invariably of amount of efforts put into it."
- pkstn 8y agoThat’s not the case with RE:DOM, since you have a single update function to make pure updates. I usually create a requestAnimationFrame debounce to have just a single render per animation frame.
- anonytrary 8y agoHis point is that writing the single update function becomes complex when you have lots of changes to apply.
- pkstn 8y agoThe beauty is that you know exactly what’s happening and when. Debugging is also way easier without long stack traces. There’s pros and cons in everything.