Any suggestions on a HTML/CSS/JS TreeView that fits into the LiveView environment

[MarthinL]

@garrison

The problem is that imperative frontend UI forces the developer to reason about exactly which parts of the UI must be updated when the state is changed. For reasons I have laid out in previous comments, this is intractable for any non-trivial use case.

But I should not have to substantiate this further as, as I mentioned previously, the React model (declarative) has been universally adopted, including by Phoenix LiveView - unless you use streams.

There is one, and only one, point I am making here: Abandoning declarative rendering for performance is rarely a worthwhile tradeoff, and should be done with extreme caution.

OK, as topical and interesting as this discussion has been, it really is way off the topic of my original question. I have a genuine and real-world interest in handing my use-case both effectively and efficiently without resorting to any of the mesures you’ve described as the undoing of streams.

I’m moving this to a Discussion on Recursive Streams, as participants on this topic, please join me there @zachdaniel, @garrison, @derek-zhou, @cmo and @LostKobrakai