willybrauner
Re:Signals, the push-pull based algorithm
on Monday April 06, 2026 @05:59AM (#47658878)
But as the article points out, this is a naive implementation. It could be discussed and greatly improved.
Re:Signals, the push-pull based algorithm
on Monday April 06, 2026 @05:57AM (#47658850)
I create a new copy of the Set because the functions called during the loop might modify it by removing elements via cleanup functions. Without a copy, iterating directly on the Set could cause unpredictable behavior.
Re:Signals, the push-pull based algorithm
on Monday April 06, 2026 @05:56AM (#47658843)
Writing technical articles without adding a graphic and playful touch would indeed interest me less. I find that it's the intersection of these two worlds that makes reading enjoyable. Thanks for your kind words!
Re:Signals, the push-pull based algorithm
on Monday April 06, 2026 @05:06AM (#47658504)
I didn't know about Flapjax, thanks I'll check it out. Glitch-freedom is indeed a gap in this article. I focused on the signal algorithm exclusively without some implementation optimisation like batching updates; there is so much more to cover! Maybe in a next one, Thanks!
Re:Signals, the push-pull based algorithm
on Monday April 06, 2026 @04:31AM (#47658283)
I searched for the "right way" to explain this algorithm, and ultimately parsing the code was the clearest for me. This isn't always true; sometimes a graph or an interactive module has more impact; it really depends on the topic. Thanks for the feedback.
Re:Signals, the push-pull based algorithm
on Monday April 06, 2026 @04:18AM (#47658218)
Thanks a lot! The left column containing the text is sticky, The right column is absolute and translate on Y and depend on an intersection observer triggered by each scroll section from the left.