A modern programming language that makes developers happier.

kotlinlang

So, the problem with <@U78L28DMX>'s code is that she's using `Node.cache` without binding statements, effectively locking the contents of the cell to whatever item it was displaying first.

Amazing guys!  Nice work.  Solution indicates I don't need the cache, but what is the cache best used for when you *do* bind the statements?

It's a trade off I think. the `graphic = cache {}` solution uses less memory but is harder to reason about than `cellCache`, since the latter will automatically cache per item. The best solution, especially if your node graph is complex, is you use a cell fragment. That needs to be understood too though, and it might not be well enough documented but I did greate a video on it.