I think the main issue is you're using "reactive" to mean something specific that you're not stating. The web is always going to have the DOM as its tree, so a

I think the main issue is you're using "reactive" to mean something specific that you're not stating. The web is always going to have the DOM as its tree, so a system where one thing updates in reaction to another thing updating is always going to need to be explained in terms of DOM mutations, and their timings. The post details multiple ways of doing that, all of which are reactive by some definition. So, if you're saying it needs to be "reactive", it isn't of much value unless you detail how that works and how it's different to what's proposed.